Access database locking out and/or corrupting on Windows 2k.
Need urgent help with this whole organisation heavily relys on an access2 database which almost runs the place (college) basically we moved over to windows 2000 in the summer (from nt4/9x) and recently the database (specifically one file) is getting locked out frequently and occasionally corrupting! About 100+ user ...
Need urgent help with this
whole organisation heavily relys on an access2 database which almost runs the place (college)
basically we moved over to windows 2000 in the summer (from nt4/9x) and recently the database (specifically one file) is getting locked out frequently and occasionally corrupting!
About 100+ users with user privalages but full access on the network share its on plus 10ish admins accessing it.
Now we have some rough info that service pack 3 can cause this but its a bit hazey...
anyone had anything similar?
NEED HELP BAD!
whole organisation heavily relys on an access2 database which almost runs the place (college)
basically we moved over to windows 2000 in the summer (from nt4/9x) and recently the database (specifically one file) is getting locked out frequently and occasionally corrupting!
About 100+ users with user privalages but full access on the network share its on plus 10ish admins accessing it.
Now we have some rough info that service pack 3 can cause this but its a bit hazey...
anyone had anything similar?
NEED HELP BAD!
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Well, here's a couple of things you could try. First, get the latest MDSC and Jet DB components for the server (if you can do this for the clients, that would be recommended as well) as these dictate the management of data control in the OS. You can get these at www.microsoft.com/data. Next, you could check out this article:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q296264&
I had a similar issue before with a COBOL-based (ick) application, and adjusting those keys fixed it. For some reason, several workstations would lay claim to the same files/db at the same time and not release, and this addresses that behavior.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q296264&
I had a similar issue before with a COBOL-based (ick) application, and adjusting those keys fixed it. For some reason, several workstations would lay claim to the same files/db at the same time and not release, and this addresses that behavior.
no chance of converting/upgrading, were getting stumped with the "its worked since 1994" line from him
seems ok now, problem may be down to a faulty machine crashing it out (typical) however thanks all for the mega helpful advice, im going to look into sql myself so may check the tips
cheers
seems ok now, problem may be down to a faulty machine crashing it out (typical) however thanks all for the mega helpful advice, im going to look into sql myself so may check the tips
cheers