Tuesday, 20 August 2013

Can't eliminate Access corruption

Can't eliminate Access corruption

My firm's Access database has been having some serious problems recently.
The errors we're getting seem like they indicate corruption -- here are
the most common:
Error accessing file. Network connection may have been lost.
There was an error compiling this function.
No error, Access just crashes completely.
I've noticed that these errors only happen with a compiled database. If I
decompile it, it works fine. If I take an uncompiled database and compile
it, it works fine -- until the next time I try to open it. It appears that
compiling the database into a .ACCDE file solves the problem, which is
what I've been doing, but one person has reported that the issue returned
for her, which has me very nervous.
I've tried exporting all of the objects in the database to text, starting
with a brand new database, and importing them all again, but that doesn't
solve the problem. Once I import all of the objects into the clean
database, the problem comes back.
One last point that seems be related, but I don't understand how. The
problem started right around the time that I added some class modules to
the database. These class modules use the VBA Implements keyword, in an
effort to clean up my code by introducing some polymorphism. I don't know
why this would cause the problem, but the timing seems to indicate a
relationship.
I've been searching for an explanation, but haven't found one yet. Does
anyone have any suggestions?

No comments:

Post a Comment