Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database continually being corrupted

Status
Not open for further replies.

webcats

Programmer
Apr 24, 2002
60
US
Hi all,

I have a multiuser (about 25 users) database which is split into a front end/back end setup. Everything was working fine when I had the front end on the local hard drive of my users' PC, and the back end data tables on the server.

Then I moved the front-end mdb to the server also. As soon as people started opening the database and updating records, the database would get corrupted about every 30 minutes. I would have to kick everyone out and then Compact/Repair the back end database.

After 1 day of this I decided to move the front end back onto my users' hard drive - the same way I had it before. But I'm still getting a corrupted back end database. I upgraded everyone to O2K SP3, but that didn't help. The only difference is that now the database only(!) gets corrupted about every 3 hours.

Anyone have any ideas? I'm at my wit's end.

 
Hi

In my experience if you have a FE/BE set up the most frequent causes of corruption (excluding badly written application) are:

Users exiting without closing db, eg switching off pc

Power failure on server or PC

Network problems eg time outs, duff NIC cards

Since your application was orginally running OK, it is reasonable to assume that something has changed to upset it. You made one chaneg which you have reversed, but has something else chanegd, do you haev a new user who does not follow the rules, have you added new hardware etc etc

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now - UK
 
Here is my GUESS about your problem. At some point the backend was messed up. Who know what caused it. You keep doing "compact and repair" but that does not fix the underlying problem. One possibility would be to create a new blank .mdb and then import all of the objects from the sick .mdb. That would give you a fresh start.



 
Thanks for the tips guys. I'll create a new .mdb... that's a quick thing to try.

And I'll have to talk to IS about server problems.

Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top