DB Corruption

[tranchemontaigne]

I have a MS Access database that recently had a BLOB like feature added to support the storage of documents.

Since this feature was added (and documents started being stored) the DB has not behaved especially well.

For exmple, every time I run a compact/repair operation on the database something always corrupts - ususally a form or form module. When a form module corrupts code that has been working fine for months will start popping errors. When a form corrupts it will appear in the database window, but will be unable to be found at runtime. Attempts to rename and/or the corrupted form also fail because the "object cannot be found. Attempts to import an older copy of the corrupted form objects then generate errors about modules and functions existing with the same names.

The only way I have been able to resolve these errors has been to create a new empty database and import all objects except for the corrupted one, then impoort an older copy of the corrupted object from a second database.

As you can imagine, the whole process gets a little tedious.

Does anyone have thoughts or suggestions beyond separating the data tables from the forms, modules, and reports?
________
Maine Dispensary

 

[Dennisk]

Split your db into Front/back End, and store the link to the document not the document itself.

 

[jsv2002]

Also once split the front end will be distributable to other users which will improve network performance as they are running the front end locally, and you can do any design work without "locking out" other users just distribute your modfied front end.