Database Corruption

[EEK]

I inherited this user written multi user (<=10 simultaneous users) Access 2000 database. The front end in Access 2000, the back end is SQL 2000. All the tables are linked to SQL.
When the users were running the Access front end on a Novell server there were no problems. We have sinced moved it to a Windows 2000 server and are now getting a Database needs to be repaired message 2 or 3 times a day.
I searched the web and the only thing I came up with is that the Opportunistic Locks Setting on the Windows 2000 server needs to be disabled.
Naturally our server team is reluctant to change the settings.
Has anyone else experienced this problem or have any suggestions?
Right now our solution ws to put a copy og the Access frontend on each user's C:, very ugly and difficult to maintain!
Thanks so much for your help!

 

[RuralGuy]

Here is a link to several articles on splitting the db to FrontEnd/BackEnd. Database Splitting Information
I believe you will find they *all* strongly recomment putting a copy of the FrontEnd on each user's PC. If updating the FrontEnd is an issue then examine this link. Auto FE Updater

 

[EEK]

Surprised

I'm surprised to see anyone advocating copying an ACCESS Frontend to every user's C: drive. What a maintenance nightmare! Every itty-bitty change to the db requires a new copy on everyone's PC, what a hassle if you've got a large user base, or users in different cities.

 

[RuralGuy]

If you do the research you will discover that most, if not all MVPs make this recommendation, and with good and well documented reasoning.