2
Access2003,
Windows XP Pro OEM user OS,
Windows Sever 2000 server OS.
Not-so-recently I inherited 3 Access DB's from another company merging with our own. Our own system works off of SQL server, but mainting these databases is critical to keeping the business running. 1 database in particular has been causing problems. Along the course we have had a few problems with random records corrupting (new and old) and Values within fields dissapearing, which are formatted text-boxes (checked With VB code as opposed to locking down the fields to a certain type, which i believe is part of the problem).
In the past: records would courrpt, users would recieve the relevant Run-time error and the database would be compact/repaired and then everything would operate normally for a spell. However after a time, it got to the point where records would corrupt and a repair would not work. Halfway through the Compact/Repair process Access stalls and gives a message that it has to restart. A copy of the database it made (incomplete) and placed in the same directory named DB* (where * is an incrimental number based on how many copies of the DB exist inthe current directory). Again this wasn't a big problem, as i have scheduled (along with daily backups) an hourly back of each of the 3 databases, which normally is faster than repairing the database and means at most an hour of work is lost.
The most recent issue however is that a very old record that hadn't been accessed in months corrupted, this went un-noticed until recently and now it's too late to restore from a backup. the compact/repair still does not work - and other repair facilities (the jet engine repair util for example) crashes while trying to repair it also. I have tried going into the back end, but as soon as i try to remove the corrupted records, it becomes impossible to save the changes due to the "unrecognised database format" error message.
These systems will be moving onto our own, more powerful database engine and workflow management system soon, but this corrupted record will not allow exporting of records, as this also crashed accesss. So until this issue is resolved we are unable to push forward with the migration and i have been unable to find a solution to the problem.
If anyone has any ideas, it's all appreciated - i have been working on this for weeks as it stands - im at the point of trying anything!
