"Error Message: Error Accessing File. New connection May have been lost."

[RBB]

I get the error "Error Message: Error Accessing File. New
connection May have been lost." I am using Access 2000 and
have VBE6.dll version 6.3.91.8. I have looked at the
knowledge Base article 304548.

My large Access 2000 program keeps giving the error and is
working strangely, is there any way to fix this without
going thru all the step MS stated? It would take me days
to do what they say. How did this happen, and is it going
to happen again. I cannot see any MS code to fix the
problem; like a new VBE6.dll code.
Help, it taken me months to write this program and it is
not working and I need it. Back -p file is way out of date.

RBB

 

[Dirk Goldgar]

I get the error "Error Message: Error Accessing File. New
connection May have been lost." I am using Access 2000 and
have VBE6.dll version 6.3.91.8. I have looked at the
knowledge Base article 304548.

My large Access 2000 program keeps giving the error and is
working strangely, is there any way to fix this without
going thru all the step MS stated? It would take me days
to do what they say. How did this happen, and is it going
to happen again. I cannot see any MS code to fix the
problem; like a new VBE6.dll code.
Help, it taken me months to write this program and it is
not working and I need it. Back -p file is way out of date.

You can keep the corruption from happening again either by applying SP3
as recommended in the KB article, or by remembering always to compile
immediately after importing any object that has a code module, before
saving. I *strongly* recommend also that you apply SP3, or sooner or
later you're going to forget and be bitten by this bug again.

Unfortunately, neither of the above-mentioned steps will fix the
corruption to your database that has already occurred. I think your
best approach is to try importing all the objects into a new database,
skipping any object that won't import due to the corruption. Then
compile and save the project. Any objects that won't import will have
to be recreated manually or else restored from your backup. If you have
to recreate an object, you may try just discarding its code module (by
setting its HasModule property to No and saving it) and rebuilding just
that. I haven't had to do this, though, so I don't know for sure that
it will work.