I am not sure where to post this so please let me know if it needs to be moved to a different section.
My Question concerns an Access Database 2003 that is being shared on a network share, after it is used for a while the database becomes corrupt and has to be restored, and this happens frequently.
When a user exits the DB it would warn them that it was corrupted and it was going to be compacted, repaired, and renamed, after that it was deleted and a file with the name of db1.mdb was created.
This database has been converted from a prior version of Microsoft Office Access by using the DAO Compact Database method instead of the Convert Database command on the Tools menu (Database Utilities submenu). This has left the database in a partially converted state.
The database would open but certain tables were missing data or would not open.
In each instance the DB would grow 3 – 4 meg in size.
The file server is:
Compaq ML570 with 1 GB ram and close to 500 GB disk storage.
Fedora core 6.
All users have full permissions to the share.
veto oplocks is on for all files that relate to mdb .
Windows XP SP2
MS Access 2003
2 GB ram
3 Ghz proc
All machines are on the same subnet, and the users have 2 switches and 1 fiber hub to cross to get to the server.
Switch on their floor -> Fiber Hub -> Switch where servers and lan come together
On the server, Ethereal, and ifconfig show 0 errors on the interfaces
This File server services 5 other groups with no problems, but this is the only Access DB.
The DB was setup according to vendor instructions and is split.
The Access DB backend is about 10 MB.
Should this be moved to a Windows Server? My only other experience with a shared Access DB was at another company about 5 – 6 years ago and I remember having to occasionally restore it for the users. I seem to remember that the errors had to do with a compact of the db. Those servers were NT 4 and 2000.