Microsoft Access 2000 - "Error Accessing File. Network connection may have been lost."

Most likely corruption ...  try this procedure:

A **DeCompile** may help here ...

But first, if you have not already:
Check for any **Missing References via the VBA Editor>>Tools>>References ....

Then, follow this procedure:

0) **Backup your MDB**
1) Compact and Repair the MDB, as follows:
Hold down the Shift key and open the MDB, then from the menu >>Tools>>Database Utilities>>Compact and Repair ...
2) Execute the Decompile (See example syntax below) >> after which, your database will reopen.
3) Close the mdb
4) Open the mdb and do a Compact and Repair (#1 above).
5) Open the mdb:
    a) Right click over a 'blank' area of the database window (container) and select Visual Basic Editor. A new window will open with the title 'Microsoft Visual Basic' ... followed by then name of your MDB.
    b) From the VBA Editor Menu at the top of the window:
       >>Debug>>Compile
        Note ... after the word Compile ...you will see the name of your 'Project' - just an fyi.

6) Close the mdb
7) Compact and Repair one more time.

*** Executing the DeCompile **EXAMPLE**:
Here is an **example** of the command line syntax  (be SURE to adjust your path and file name accordingly) for executing the decompile:

Run this from Start>>Run, enter the following command line - **all on one line** - it may appear like two lines here in the post:
Also, the double quotes are required.

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile "C:\Access2003Clients\YourMdbNameHERE.mdb"

For more detail on the Decompile subject ... visit the Master on the subject (and other great stuff) Michael Kaplan:

http://www.trigeminal.com/usenet/usenet004.asp?1033

mx

That error message is VERY misleading ... and almost always means the MDB is corrupted.  The Decompile will *usually* fix the corruption.

mx

I am having problems following the steps.  The same error message occurs during the compact and repair - due to the switchboard opening.  I used the command line switch and it did throw an error that alerted me to something new.  

When I copied the form (the reason this all happened) I named it frm_Test.  I deleted the form from access, but the module Form_frm_Test still exists in my project.  I don't know how or it will not allow me to remove it.

Don't know if I should try the MS solution?

I tried new database and just importing straight all forms and modules etc.. Still had the error.

Used the MS solution: http://support.microsoft.com/?kbid=304548

Don't know why they assume/suggest it only applies to that certain DLL version.  I also upgraded to the office sp3 before doing the procedure.  I don't know why I didn't have that update - I use automatic updates and religious check Microsoft update and it didn't say I needed any updates.  But after installing it all my office products say SP3 in about box... (They didn't before).  So hopefully that helps this from happening again, but thats most likely wishful thinking!

Thanks mx!

I didn't clearly state that the solution was to follow the procedure outlined here:
http://support.microsoft.com/?kbid=304548

Its working again...