Scenario:
Access database, VB front end , 2-30MB in size, up to 300 tables
Multi-user, typically 1 to 5, sometimes 10 users..
What Happens:
At one site, the one with most users, there have been occasions when one user cannot open the file, which denies it is Access. Meanwhile other users are still happily working in the file.
Occasionally, on only one site (out of 10) there is a problem and the file denies being an Access database to everyone. Most times it is possible to use repair from VB to fix it, sometimes repair is only possible in Access. Once at this site the database that was sent back for recovery had been upgraded to 2000 and users said they did not do that. They only have Access2000, not 97, the VB uses Jet 3.5
Now, for the first time, the DB is unrecoverable.
What I have tried to stop this
The program uses calls to MSLDBUSR.DLL to determine if more than one user has the app open and prevents (or at least just advises against) large-scale operations when there is more than one user. The users who have had the problem were not doing such things.)
I have now extended the use of MSLDBUSR.DLL so that when a suspect user session is found users are advised to log off and repair the model. (I have made this countable as it seems one such event may clear soon after).
I have spent the day running multiple sessions, and breaking the network or switching off one of the PC’s in the middle of major operations to try to break it.
I have not yet managed to break a file, but I have reached one repeatable situation, by pulling the plug:
MSLDBUSR.DLL reports that no users have the file open.
Attempts to repair the file report “File in Use”. This applies even when the File has no associated LDB file.
Rebooting the PC (the one with the file on it it) fixes the problem.
I have thought about the things that are different at the site that has the problems. Just in case anyone recognises something here they are:
The users are young grudautes, not in computers but in another scientific technology.
They use very long files names such as
P:\Department\ projects\project 11xyz\ Myproject11xyz(working)2002-03-03.ext
Any Suggestions?
Access database, VB front end , 2-30MB in size, up to 300 tables
Multi-user, typically 1 to 5, sometimes 10 users..
What Happens:
At one site, the one with most users, there have been occasions when one user cannot open the file, which denies it is Access. Meanwhile other users are still happily working in the file.
Occasionally, on only one site (out of 10) there is a problem and the file denies being an Access database to everyone. Most times it is possible to use repair from VB to fix it, sometimes repair is only possible in Access. Once at this site the database that was sent back for recovery had been upgraded to 2000 and users said they did not do that. They only have Access2000, not 97, the VB uses Jet 3.5
Now, for the first time, the DB is unrecoverable.
What I have tried to stop this
The program uses calls to MSLDBUSR.DLL to determine if more than one user has the app open and prevents (or at least just advises against) large-scale operations when there is more than one user. The users who have had the problem were not doing such things.)
I have now extended the use of MSLDBUSR.DLL so that when a suspect user session is found users are advised to log off and repair the model. (I have made this countable as it seems one such event may clear soon after).
I have spent the day running multiple sessions, and breaking the network or switching off one of the PC’s in the middle of major operations to try to break it.
I have not yet managed to break a file, but I have reached one repeatable situation, by pulling the plug:
MSLDBUSR.DLL reports that no users have the file open.
Attempts to repair the file report “File in Use”. This applies even when the File has no associated LDB file.
Rebooting the PC (the one with the file on it it) fixes the problem.
I have thought about the things that are different at the site that has the problems. Just in case anyone recognises something here they are:
The users are young grudautes, not in computers but in another scientific technology.
They use very long files names such as
P:\Department\ projects\project 11xyz\ Myproject11xyz(working)2002-03-03.ext
Any Suggestions?