We have a split database. BE on server and FE on 3 user machines.

If more than 1 of us are accessing the same BE table we often get the message "Locked. Could not update" when we go to print a record or move to the next record.

Now, the FE is identical on all 3 pcs.

e.g. When this happens on PC1 or PC3 and we close the open form on PC2 it resolves the problem.

I have tried all the built in record locking options.
Currently I have it set to "No Locks" and "Open database using record-level locking" is NOT checked. Open mode is "shared".

Can anyone suggest a solution?

How should the record locking be set? The 3 users never need to have access to the same record at the same time.

Thanks

Paul

are any of your queries properties (right click the design pane and select properties) set to locks, even though the default is set to no locks

it sounds like the table IS getting locked somehow

I have one query which gets the relavent data from a table for the form we're using.

jpg attached.
It seems to be set to No Locks

Also, should have said that all 3 users are using Access 2003 Runtime to run the FE.

on the form properties, the format sheet also has a record locks setting. could this be set to something inappropriate

I have never seen the message you are quoting. Occasionally with no locks you will get "another user has modified your record", and this is often just a programming issue.

The form properties was also set to No Locks.
I have it now set for Edited Record.
Will see how that goes but am sure I've tried this before lol

Same error occurred less than an hour later with only 2 users on the database.

Settings just now are:
Default Record Locking: Edited Record
Open databases using record-level locking: ON

Form - Record Locks: Edited Record
Query - Record Locks: Edited Record


----------------------------------------
Now trying the following settings:
Default Record Locking: No Locks
Open databases using record-level locking: ON
Form - Record Locks: No Locks
Query - Record Locks: No Locks

Any other ideas?

I have the exact same problem. I have used this db for one year without any issues and three weeks ago I got the same message "could not update, currently locked" but after a few minutes if went away. Now it has shown up again and I am not sure why. Four users on board at this point, All of them full users, none of them admin. Not sure what to do.

mafhobb

What settings do you have mafhobb?

Default Record Locking: ?
Open databases using record-level locking: ?
Form - Record Locks: ?
Query - Record Locks: ?

Are you all putting records into the same table?

I will let you know how I get on with my modified settings.

Cheers

perhaps there is a corrpution in the be database

try doing a compact/repair on it, see if that helps

I got the error to go away, although I am not sure why.

I had 3 people onboard (including me). One of the users was entering data in a form (A) that goes into a table (B). Someone else was also entering data in that same form A to add data to that same table, and I was trying to do that too.

What I have found is that the 1st user opened the form and started entering data, but did not complete entering it and basically had the cursor in one of the form fields.

The 2nd user entered data (apparently he started entering it after the 1st user started entering his data) in the form and had exited the form (the data was visible in the form), but I noticed that his data was not visible in the table.

The 3rd user (me) opened the form after the 1st user had started entering data but I am not sure how it was in relation to the 2nd user. Anyway, each time I tried to enter data, it would give me the error mentioned above.

So, I went to the 1st user and got him to finish his entry and close the form. Results: Neither his entry nor the entry from the 2nd user showed up in the table and I still got the error message.

The next step was to ask the 2nd user to shut down Access (since he was already out of the form). When he did this, both the 1st user and 2nd user entries finally showed up in the table and my error disappeared.

It all has been working fine since.

Weird.

just one thing

are you sure the users are using the fe on their own pc

could they inadvertently be both using the same network copy