A ghost blocks a table's fields 2

[kupe]

Users use the table in a small database, accessing it from both the table and the form. A fault develops. When I try to go to the fields, Access tells me that someone else is using the table. A (thorough) check shows that no-one else is anywhere near the database.

Anyone had this problem before please? And did you find an answer please?

Cheers from an unusually warm spring day in England.
Kupe

 

[hymn]

check your record locking it sounds as if you it set to all records or you have the default open mode set to exclusive

Hope this helps
Hymn

 

[kupe]

Brilliant, Hymn,very grateful.

 

[WildHare]

And NEVER EVER EVER give a user direct table access.. shudder....

Did you ever see a user hit CONTROL/A and then the DELETE key all in one motion....???

If Confirm Deletions is turned off , you don't even get a prompt....

Yikes.

Jim


Me? Ambivalent? Well, yes and no....
Another free Access forum:

http://www.forumco.com/jmhare

More Access stuff at

http://www.jmhare.com/wildhare2.htm

 

[kupe]

H Jim

Thanks for the advice. But how can you stop you boss twiddling?

Could you use your philosphy for a client-company? Wouldn't it be rather difficult to keep the tables from them if the tables contain their info?

Gratefully
paul

 

[WildHare]

Granted, sometimes it might seem impossible to keep a semi-knowledgable user from accessing the tables directly. But it's always worth the effort to wrap your application entirely within forms and prewritten queries to control navigation and operation. You're not keeping them from their data, you're protecting them from themselves. Once you explain how tables just contain raw data, but your forms and queries will present it to them in any manner they choose, they usually understand.

I ONLY deliver 'black box' apps to client companies, and they know that ahead of time. There's no Access menu bar, no toolbars, no database window or anything that needs "explaining". A modal menu form controls all movement within the system. I use text based command buttons or clickable labels for all actions, since not everyone knows what the stupid little triangle with the asterisk means.

If the 'boss' insists on 'twiddling', make sure s/he understands that if s/he corrupts the data, you will charge DOUBLE for recovery and rebuilding efforts. Get it in writing, if possible. I did this once, and it never came up. I know that every now and then you run into the person who thinks s/he "knows Access" and insists on direct access to tables. In this case, you simply have to make sure that the powers that be are AWARE of your stand against this, and WHY.

Don't mean to ramble, but this is an extremely important facet of delivering usable, correct and functional application systems.

Jim



Me? Ambivalent? Well, yes and no....
Another free Access forum:

http://www.forumco.com/jmhare

More Access stuff at

http://www.jmhare.com/wildhare2.htm

 

[kupe]

Your profile speaks for your knowledge, Jim. Very thankful to learn such an important point. Gratefully
paul