Database Corrupt

[ITTony]

   We are running Intellitrack Check In/Out v.5 with Access 2003.  It took us many months to get all of our data into the database and now we have been running the application in production mode for almost 6 months. 

  We have been experiencing a reoccurring problem with database corruption.  Of course once we get the "Database Corruption" error, there is no way to get back into application without either reinstalling the application or restoring it from tape backup.  The "Compact/Repair" function never works to repair the corruption.

   When I state that this is a reoccuring problem, I mean that this happens usually, on average, about once a week.  This is pretty ridiculous because our database is not even heavily used all day, nor does it ever become very large.  The largest I have ever seen it get is perhaps 225MB.  Usually it doen't get over 175MB before it becomes corrupt. 

   In an attempt to be proactive, I set up a batch file through Windows task scheduler, that runs a compact/repair on the database EVERYDAY.  Even with running a compact and repair everyday, the problem still persists.  This is totally unacceptable.  I don't see what we could be doing to cause the corruption.  We simply use the application as it is intended to be used and nothing more.  Is there something we could do more proactive than just compact/repair in order to prevent this?

Thank you

[louk]

When the access workstation database reports the corrupt error it does require to reinstall from CD. It is important when reinstalling from CD to select workstation instead of full or server when prompted. You can then create a copy of the C:\ITCHECK5\ITCHECK5.mdb and copy this to  another folder. The next time you receive this error message you can simply copy this good copy of the workstation file back to the C:\ITCHECK5 directory and overwrite the existing ITCHECK5.mdb and this will correct the problem. Hope this helps!

[ermnet]

What we did is we change the IT shortcut to a batch file that first copies a fresh mdb from a backup directory to the ITASSET directory. No more DATABASE corruption error. The draw back is that that it takes a bit longer to start.