"Error Accessing File: Network Connection May Have Been Lost"

[Drew]

The error in the subject is one I am suddenly getting in
the database I am developing. It occurs when the MainMenu
form loads. The database had been working fine and then
one day I noticed that the SelectVendor form, which is
selected using a commmand button on the MainMenu form, was
missing. Apparently I had accidently deleted it. I
imported the SelectVendor form from one of the database
backups and figured everything would be find. Now,
however, when I open the MainMenu form, I immediately get,
"Error Accessing File: Network Connection May Have Been
Lost". This error is doubling confusing since I am not
connected to a network.

Nothing seems to be out of whack with the VBA code. I
imported the SelectVendor form from several backups, but in
each case the error occurs.

Has anyone experienced this and/or have a solution?

Thanks,
Drew

 

[Dirk Goldgar]

The error in the subject is one I am suddenly getting in
the database I am developing. It occurs when the MainMenu
form loads. The database had been working fine and then
one day I noticed that the SelectVendor form, which is
selected using a commmand button on the MainMenu form, was
missing. Apparently I had accidently deleted it. I
imported the SelectVendor form from one of the database
backups and figured everything would be find. Now,
however, when I open the MainMenu form, I immediately get,
"Error Accessing File: Network Connection May Have Been
Lost". This error is doubling confusing since I am not
connected to a network.

Nothing seems to be out of whack with the VBA code. I
imported the SelectVendor form from several backups, but in
each case the error occurs.

Has anyone experienced this and/or have a solution?

If you're using Access 2000, see this KB article describing the nasty
bug that has bitten you:

http://support.microsoft.com/default.aspx?scid=kb;[LN];304548

Office 2000 SP3 fixes the bug, but that won't repair your corrupted
database. You'll have to resort to a backup, or else try importing all
objects to a new database -- some objects probably won't import, and
you'll have to recreate them from scratch. When you do import the
objects, unless you've applied the service pack, it is *crucial* that
you compile and save the project before closing the database.

 

[Drew]

-----Original Message-----

If you're using Access 2000, see this KB article describing the nasty
bug that has bitten you:

http://support.microsoft.com/default.aspx?scid=kb;[LN];304548

Office 2000 SP3 fixes the bug, but that won't repair your corrupted
database. You'll have to resort to a backup, or else try importing all
objects to a new database -- some objects probably won't import, and
you'll have to recreate them from scratch. When you do import the
objects, unless you've applied the service pack, it is *crucial* that
you compile and save the project before closing the database.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

Oh man, that is nasty. I am using Access 2000. Thanks for
the info. Suddenly I have a tremendous headache.

 

[Dirk Goldgar]

Oh man, that is nasty. I am using Access 2000. Thanks for
the info. Suddenly I have a tremendous headache.

Fortunately, you have backups. I hope that anything you can't recover
from the corrupted database, you can get from a backup. Good luck.

 

[Guest]

Thanks...unfortunately I put in quite a bit of code from
the previous backup..hopefully this will not be a very long
process.