Could not update; currently locked.

[Guest]

I keep getting the message "Could not update; currently locked." when trying to use a drop down menu in an access table. Actually it is two tables that have a relationship. In the main table you click a little plus sign which makes the secondary table pop-up. And its a drop down menu in this second table that is messed

The db is shared with about 30 users. It does not happen all the time, but its really frustrating for the users. I am running a Win2K network with Win2K and WinNT clients. If I go around and ask everyone to close down access and then go back in, it works, but this is time consuming and really annoying

Can anyone help me, has anyone seen this before? Should I be asking users to close the db down when not in use

Thanks in advance for any help

Jeff

 

[GVaught]

Is your database split? Most problems of this sort usually occur because a
database isn't split.

I keep getting the message "Could not update; currently locked."

when trying to use a drop down menu in an access table. Actually it is two
tables that have a relationship. In the main table you click a little plus
sign which makes the secondary table pop-up. And its a drop down menu in
this second table that is messed.

The db is shared with about 30 users. It does not happen all the time,

but its really frustrating for the users. I am running a Win2K network with
Win2K and WinNT clients. If I go around and ask everyone to close down
access and then go back in, it works, but this is time consuming and really
annoying.

Can anyone help me, has anyone seen this before? Should I be asking

users to close the db down when not in use?

 

[John Vinson]

I keep getting the message "Could not update; currently locked." when trying to use a drop down menu in an access table. Actually it is two tables that have a relationship. In the main table you click a little plus sign which makes the secondary table pop-up. And its a drop down menu in this second table that is messed.

The db is shared with about 30 users. It does not happen all the time, but its really frustrating for the users. I am running a Win2K network with Win2K and WinNT clients. If I go around and ask everyone to close down access and then go back in, it works, but this is time consuming and really annoying.

Can anyone help me, has anyone seen this before? Should I be asking users to close the db down when not in use?

Thanks in advance for any help,

Jeff

Two suggestions:

- As noted elsethread, run, don't walk to the Database Splitter
Wizard. The tables should be in a single shared "backend" database;
each user should have a frontend linked to the tables.

- Create a Form with a Subform rather than using table datasheets. If
you have two users with a Form open they'll run into this problem much
less often than if they're editing the same Table.

 

[Guest]

Thanks for the help guys, I think that should do it.

 

[ABC]

Thanks for the help guys, I think that should do it.

when trying to use a drop down menu in an access table. Actually it is two
tables that have a relationship. In the main table you click a little plus
sign which makes the secondary table pop-up. And its a drop down menu in
this second table that is messed.but its really frustrating for the users. I am running a Win2K network with
Win2K and WinNT clients. If I go around and ask everyone to close down
access and then go back in, it works, but this is time consuming and really
annoying.