"Error accessing file. Betwork connection may have been lost"?

  • Thread starter Thread starter MJuric
  • Start date Start date
M

MJuric

I get this error trying to run a mailing label report that I've run
several times before. to my knowledge nothing has been changed, and
the netqork and access to the file is fine. All of teh otehr reports
work in the same DB. Somthing wierd has been going on with this DB
since I created. Any integrety type checks one can run on an Acces DB
to try and correct things?

~Matt
 
Hi Matt,

I think you've been stung by a particularly nasty bug in
Access 2000. Sure sign is that dreaded "Network Connection
may have been lost.." messsage. Details about it can be
found here:

http://support.microsoft.com/?id=304548

The corruption in your database may not be recoverable.
You might try importing everything into another database.
I believe this bug is fixed with Service Pack 3, but it
will not *fix* corruption already present. To avoid this
bug you absolutely, positively, have to compile your
database EVERY time you import something.

Also, (from Dirk "Yoda" Goldgar) one other thing you might
try first is decompiling your database -- or rather, a
copy of it. Instructions for how to do this may be found
here:

http://www.mvps.org/access/bugs/bugs0008.htm

and here:

http://www.granite.ab.ca/access/decompile.htm

This was also posted recently from someone from Microsoft:
326605 ACC2000: Issues Fixed in Access 2000 by Office 2000 Service Pack 3
http://support.microsoft.com/?id=326605

304548 ACC2000: Error Message: Error Accessing File. Network Connection May
http://support.microsoft.com/?id=304548

After applying Office 2000 sp3 you are going to need to salvage your
database modules (Standard, Forms/Reports) by saving them out to text
files. Example:

- Open Form/Report in design view and select menu option View > Code
- Select the menu option Edit > Select All (to select vba code)
- Select menu option Edit > Copy
- Paste in Notepad file
- Close VBA window to return to Form/Report
- Within the properties Window of Form/Report change the property "Has
Module" from "Yes" to "No"
(this will delete the code behind the object)
- Save your Form/Report
************* Repeat above steps for each Form/Report that has code
*****************
- For your Standard module just open and copy to text files

- Then import all your objects (within exception of your Modules) to a new
database file
- Copy the code from the above text files into new modules in your new
database
- For the Forms/Reports reverse the steps by opening their VBA modules and
pasting the code from the text files

*******************************
You can also try running decompile switch but the above methods are
normally your only shot..


I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access
Good luck,
Jeff Conrad
Bend, Oregon
 
On Tue, 9 Mar 2004 14:11:35 -0800, "Jeff Conrad"

Holy C#@!

I've got 30 some odd reports in this thing. It would take me a month
of Sundays to pull that off. The only reports that have the problem
are ones that call certain functions. Anyway of just "redefining" the
functions rather than redoing all of the reports?

Also the site you posted mentioned something about going back to an
"uncorrupted" version. I've copy and pasted several reports in this
thing, I'm assuming that's whats caused the problem, how do I tell if
an older version is corrupted?

~Matt


It mentioned reverting back to the last "uncorrupted" database.
 
Matt,

I have encountered this problem more than once (I guess I will never learn!).
When the problem occured, it invariably occured in only one object. Certain
types of modules seem most prone followed by pop-up forms with code. I have
always (knock on wood) been successful overcoming the problem by making a copy
of the database abd then systematically deleting objects until the problem goes
away which tells you the problem was in the last item(s) deleted. I then was
able to narrow down the problem to one object which had to be rebuilt. At that
point though, if it's a report or form and you can get to the design view, you
can copy and paste the form or report from design view to another design view
but you do need to rewrite the code. For me the problem always was pinpointed to
the code. The code looked okay but for whatever reason, it just doesn't work.
Another thing, you'll waste your time importing the objects into an empty
database; you also import the problem. So I suggest to start by deleting all
your modules then open the database and see if you still get the error message.
This will tell you if the problem is in the modules. If it is, you then need to
make another copy and systematically delete one module at a time to pinpoint the
offending module.
 
Does someone/anyone else other than you access this
database? If so you should check and always make a copy
for yourself just in case things like this happen. Access
has the tendency of automatically saving itself after you
close the program and certain things you do before can
mess up the program. You should also check your file for
any viruses. That could be a possiblity of your access
doing weird thing. I believe that if all I've said here
is not the answer, then I would make another mailing
label report to see if it runs without any error. I hope
this helps.

VSY
 
Back
Top