Error Accessing File. Network connection may have been lost.

[Dale Fye]

I recently upgraded to Office 2k3 SP3, and applied the hotfix. Now I am
getting the message above almost every time I try to bring an Access 2003
database home from work. The Microsoft KB indicates this has to do with
having Access 2000 and Version 6.3.91.8 of the Vbe6.dll file installed and
that you have either imported or copied/pasted forms or reports that contain
code module or standalone modules into an Access2000 database. Did this
particular version of the Vbe6.dll file come out with SP3? The resolution
(if you have a machine without this annoying vbe6.dll file) is to export
every code module (form or otherwise) in your database to a text file, then
open a new db and import all of the objects from the old db, then reimport
each of the code modules.

They don't even mention how to resolve the problem is you don't have another
machine without this version of the vbe6.dll file.

I don't have Access2000, but I still have Access XP on my machine so that I
can continue to use Speed Ferret. But if I have to get rid of Access XP in
order to get rid of this problem, I will.

Anybody else had this problem recently? Any body have a solution?

 

[Allen Browne]

I think you are referring to this kb:
http://support.microsoft.com/kb/304548
If so, it applied only to an early release of A2000, I can confirm your
belief that the issue you are experiencing is something different.

Is there something in the file that could actually be trying to access a
network/connection/file that you don't have at home? A linked table? A file
open dialog with an initial path?

Could it be anything to do with permissions? A2003 SP3 did quite a bit of
work on the security side.

A decompile would certainly be worth trying.

 

[Dale Fye]

Allen,

I was hoping you might weigh in on this. First place I went when I started
having this problem was your site, to see if there was anything there that
explained it.

This particular file had a reference to another Access file in it, and had
linked tables from a network drive at work. But I removed the reference
(even though the file it was referencing was in the same folder as the mdb),
deleted all the linked tables, compacted and closed the db. I then reopened
it and attached tables from a local BE. Then saved it again. Upon opening
it again, I still had the problem.

Never considered the decompile option, but will try that tonight.

Thanks for your feedback.

 

[Dale Fye]

Allen,

The decompile seems to have done the trick. I also forgot to mention in my
earlier post that because I have multiple users using the front end, I have
been digitally signing it at work, and removing the signature before I bring
the file home. Don't know whether this has contributed to some of the
problems as well.

I have not been in the habit of decompiling, just using compact and Repair,
and decompiling combined with the compact and repair has significantly
reduced the size of several of my databases. I think I will start doing
this with all my applications before distributing them.

Thanks, again.

Dale

 

[Allen Browne]

Excellent news, Dale.

FYI, this is the sequence I usually try first if I'm called in to
troubleshoot someone's database
http://allenbrowne.com/recover.html

 

[Tony Toews [MVP]]

I have not been in the habit of decompiling, just using compact and Repair,
and decompiling combined with the compact and repair has significantly
reduced the size of several of my databases. I think I will start doing
this with all my applications before distributing them.

Decompiling can also reduce the startup times of the database. Once
it gets to be a few seconds I decompile the MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/