Put your thinking cap on.... VB5 mystery locks on Access 97

[drosenkranz]

I'm using VB 5.0 Service Pack 3 and Access 97 to support about 40 users on a system. Sometimes users get error locking messages that indicate their update failed because their record is in use by another user when that other user is no longer even using the system.

Sometimes the offending user is just browsing is in a different table but they're reported as locking the record the user is trying to update in their table anyway.

related problem with high traffic periods. When users log off, I can still see their computer names appearing in the .ldb file long after they've packed up, logged out, and gone home.

The only thing I noticed was I failed to close the workspace and the database before the "End" statement terminating the program. Would this affect the Database on the server in any way?

Any ideas or suggestions?

 

[DougP]

Multi user problem are usually solved when you make an .MDE file out of your .MDB.

See my FAQ' on MDE files

How do I make an .MDE file
faq181-90

What is an .MDE and why do I need it
faq181-91


DougP, MCP
dposton@universal1.com

Ask me how Bar-codes can help you be more productive.

 

[MoGryph]

Just an idea, and you may have done it already but-
In the form that your users are using to 'browse' the data, you may want
to set it up so that the Record Set Type is not Dynaset, but instead "Snapshot".

That way, when they're viewing the data, they CAN'T change anything. They should only be able to change records when they access a specific record from a different form (or perhaps, create an Edit button that changes the RecordSetType from Snapshot to Dynaset prior to editing, and then in the AfterUpdate of the form, change the RecordSetType back to Snapshot. Also, for easier understanding, give some kind of visual cue as to which "mode" they're in. I haven't done the RecordSetType switching dynamically during run-time, but I assume it should work.).

As for their computer names still showing up in the .ldb file, I'm not certain what this could be.