Database corruptions

IanW

Registered User.
Local time
Today, 11:05
Joined
Sep 10, 2002
Messages
15
Hi,



I am in charge of developing and maintaining an access database written in Access version 2.0 then upgraded and changed over a number of years through to Access 2000.



The database is set up as a File/Server application with a central data file serving between 45 and 55 PCs daily. There are 2 main data tables with around 10 other tables being accessed together all day returning approx 20,000 records in each. Each table contains approx 220 fields. I know this is a high number of fields for a table to contain (I did not write this application I might add).



The Problem: At least once a day the database is crashing (Requiring repair & compact) and either losing data or corrupting records (which appear as Chinese letters or # marks all the way across). I am not completely sure whether the corrupt data is pulling the database down or is a by product of the crash. I do find corrupt (Chinese) data in the tables when the database is working, but this may, if left in then cause a crash later.



I am just looking for any advice that I can find. The database was crashing regularly when I joined the company 6 months ago, but this seemed to coincide with a mail merge happening from the database, I rectified this by using VBA to fill word templates with data using bookmarks. The database was then stable for a while but now has become very unstable. It would be a big help to find the machine (if it is the cause) that is bringing the database down but can’t think of the best way to do this, or whether it would be a particular machine that would cause such corruptions to occur.



If anyone can help in any way I would be very grateful.
 
You don't say whether your app is split into a front end and back end. If it is not, now is the time to split it. The front end can be shared on a network drive or loaded onto the individual PC's.

Corruption happens most frequently when the db is improperly closed. This happens when a user has to reboot without closing the app correctly or if a user looses his network connection. If your PC's have a power saving mode that shuts down the hard drive, this can disrupt the network connection. If the db is open at this time, corruption can occur.

Having the db split into fe and be minimizes the corruption problems.
 

Users who are viewing this thread

Back
Top Bottom