"Error Accessing File"

  • Thread starter Thread starter Julie
  • Start date Start date
J

Julie

Hi!

I have an access database hosted on a share drive which a
few people use.
I'm not sure what we did, but all of a sudden, when I try
to edit any of the reports or queries, I get the following
message:
"error accessing file, network connection may have been
lost".
If i move the database to my hard drive - i still get the
same error.
I also tried to re-create the database by copying and
pasting the data only, and continue to get this error.

If anyone has any suggestion, I would greatly appreciate
it!
 
Julie said:
Hi!

I have an access database hosted on a share drive which a
few people use.
I'm not sure what we did, but all of a sudden, when I try
to edit any of the reports or queries, I get the following
message:
"error accessing file, network connection may have been
lost".
If i move the database to my hard drive - i still get the
same error.
I also tried to re-create the database by copying and
pasting the data only, and continue to get this error.

If anyone has any suggestion, I would greatly appreciate
it!
Click to expand...

Are you using Access 2000? Could it be this bug?

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

If so, 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.

Even if it isn't this bug, you could have a corrupt VB project,
especially if several people are sharing and making changes to a single,
unsplit database on a server. (You really should split the database in
such a case, and give each user her own copy of the front-end, all
linked to the shared back-end on the server.) Your procedure to recover
from the damage is the same as if it were corrupted by that bug. Just
possibly you can recover by decompiling the database, using the
/decompile command-line switch:

msaccess.exe /decompile "C:\Your Path\YourDB.mdb"
 
Back
Top