• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 714
  • Last Modified:

Error accessing file. Network connection may have been lost.

Hi experts,

I have been working on a database that has been located on a drive through a network for the past year with no problems.  All of a sudden I have started getting the following error when I am in my forms:

Error accessing file. Network connection may have been lost.

I tried the obvious thing and that was to close down the system, and copy the db file to my local hard drive but I am still getting the error message. I have also rebooted the machine.  I have tried this db file on three computers and still get the error message.  Can anybody help?

Thank you.

Terry
0
TerenceHewett
Asked:
TerenceHewett
  • 2
  • 2
  • 2
  • +2
1 Solution
 
flavoCommented:
Could be corupt.  Try these steps:

http:Q_21477388.html#14346433

Dave
0
 
rockiroadsCommented:
Most likely corrupt. Check out the links given my Flavo
Another thing to try is to copy one form/module etc at a time to another database. Though that may not solve it, it may help you find your corruptness.
Hope u got a backup.

Remember (my current saying of the day), Access is more flaky than Cadburys!!!

Wow, 2nd time I got to use that today
0
 
Leigh PurvisDatabase DeveloperCommented:
It's still as tasty though (to me anyway) ;-)

I've had that problem with a corrupt module in a form before.
If you can get to it (or a backup of the code) copy the text of the code.
Set the form's HasModule property to No.
Save - compact yadda yadda.
Open the form - HasModule yes - paste it in.

If that works big yay - if not do all the full on corruption repairing type stuff :-)

(OK - I suppose decompile isn't exactly a huge chore lol)
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
dbase118Commented:
Are you using Access 2000?

There was a known bug which occurred because of a conflict between access 2000 and a Vbe6.dll file. It usually occurred after next generation MS software was installed on same computer as you Access 2000 load. Happened to me when Project 2002 was installed with Office (Access) 2000, but have read it can also be any XP products. Any new installs recently?

It puts the db in a state of decompile where any attempt to use anything driven by code, buttons, dropdowns, macros, switchboards, etc threw the error.  

Link to KB post on topic
http://support.microsoft.com/default.aspx?scid=kb;en-us;304548
0
 
rockiroadsCommented:
Leigh, u ever been to Cadbury's world? They give u a sample of the choclate as its being made
damn nice - sickly sweet though
0
 
Leigh PurvisDatabase DeveloperCommented:
Mmmm... the land of chocolate.  (Yap.. yap.. Chomp!)

(One for Dave there).
0
 
TerenceHewettAuthor Commented:
Thank you to all.  Dbase, that article was fab - I now have the service packs and the problem seems to have gone.

Regards,
Terry
0
 
dbase118Commented:
This was one of my most hated bugs in all of Access-land. Glad the article helped.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now