User can't update db 1

[jeffmorl]

I have a multi user (15-20 at a time) db on which users enter time (and other data) into a form which updates a table.

The db has been working with multiple users for about 18 months with no apparent problem. Until today.

Now, when someone tries to enter their time into the db and move on to a new record entry on the form, they get a "Could not update; currently locked." error message.

I was on the db earlier today and everything was fine, then all of a sudden, it thinks it's locked.

Frustrating, to say the least.

Any suggestions, ideas, help is greatly appreciated.

 

[lameid]

Assuming you are not experiencing typical lock contention...

Does someone have their default open mode set to exclusive instead of shared? Default record locking not set to No locks?

Someone NOT Have "change" - read and write - permisson tot he folder where the backend is?

 

[jeffmorl]

Right, not the usual lock issue.

I tracked down the last user to the db by looking at the time stamp w/user name on the table and paid a visit to her. Her db client settings did not indicate a record lock in any way.

She had closed the db but for some reason her computer name was still listed in the .ldb file. As were others who I know were not in the db. How is it that the lock file doesn't release the computer names of those who are, or have been in the db?

My issue is resolved, for now, but don't ask me how I did it.

The day when we move this to a web app with data on the sql server won't come soon enough.

Thanks for the feedback just the same. Much appreciated.

 

[lameid]

If access crashes or the database is corrupt, it often won't cleanup the LDB file.

I would backup, compact and repair to be on the safe side.

 

[jeffmorl]

Been there, done that.

It's a daily issue with me. I have users on the system from 6:30am - 5:00pm and after that, I would like to perform updates, modifications, etc. but can't get exclusive rights to it with that ldb file in place.

Is there a way I can remove it if I know everyone is off the system?

 

[lameid]

Compacting and Repairing should clear the LDB file assuming it runs and would be the preferred method.

However, file locks are maintained on the LDB file, so my experience is you can delete it if everyone is genuinely out... But this brings me back to Comapacting and Repariing since an orphaned ldb file is an indication of some sort of execution error.

 

[jeffmorl]

Thanks for the suggestions and advice.