Locking?!

[jacobl]

I am developing a medium sized inventory/job costing application using DAO 3.5 and Access. Lately I have been getting lots of exceptions like this:
Couldn't update; currently locked by user 'admin' on machine 'Machine'.
The strange thing is, I am being very sure to close all recordsets and there are no other open recordsets from the database the changes are being made to. Or any other databases for that matter(Only a few) This problem persists after I close the program and re-open it. For instance, I'll do something, and it works the first time, then I re-open it and do it again, and it gives me the exception. At first I thought I wasn't closing some recordsets or calling Update. But I am. What could be causing this?

Thanks,
JL

I have run into similar problems with Access. The first thing that I would check is the type of network that you are on. If that particular type of network does not support the access locking scheme you are hosed. This will happen particularly over a UNIX backbone. There are some other networks that will cuase the problem. If you are unsure you can chek the knowledge base at Microsoft.

You may alos want to check and make sure that the database isn't getting corrupted. As you probably know the system information is stored in access tables along with your database. You may want to try and run a repair.

Good Luck!

[jacobl]

I see these problems even when no others are opening the database, so it is only my application running(and my app is single-threaded)
I ran the databases through a repair in Access97 and the error changed from the previous to "Operation not supported by this type of object." but the error code stayed the same (3260) 3260 under MSDN online help is the "Couldn't update due to being locked" error.

Strange!

JL