Error cannot access file?!?

  • Thread starter Thread starter stephen.belyea
  • Start date Start date
S

stephen.belyea

Network connection lost? AHHHHH!

I've been getting this error in my Access project and now none of my
VBA code will work on any of my forms! It started when I closed my
project down on my computer and went over to another computer to keep
working on it. Now whenever I try to do anything in my project that
uses VBA code (for example, click a button), I get an error that says
"Error cannot access file. Network connection may be lost." My code is
still there, but it just won't run! I even tried cutting the code out
and repasting it to no avail. Any help here is sincerely appreciated!!!
 
Oh, dear! If this is Access 2000, you may have struck this nasty bug:
Error Message: Error Accessing File. Network Connection May Have Been
Lost
at:
http://support.microsoft.com/?id=304548

Hopefully your original machine still has a good copy of the database, so
you will be able to revert to that. It won't keep happening after you apply
the updates (unless it really is caused by trying to use the database across
an unstable network.)
 
Oh, dear! If this is Access 2000, you may have struck this nasty bug:
Error Message: Error Accessing File. Network Connection May Have Been
Lost
at:
http://support.microsoft.com/?id=304548

Hopefully your original machine still has a good copy of the database, so
you will be able to revert to that. It won't keep happening after you apply
the updates (unless it really is caused by trying to use the database across
an unstable network.)
Click to expand...

Ughh.... that's exactly what happened. I'm currently working through
the knowledge base article. Thanks a ton for the link, hopefully I can
get this sorted out!
 
Ughh.... that's exactly what happened. I'm currently working through
the knowledge base article. Thanks a ton for the link, hopefully I can
get this sorted out!
Click to expand...

Everything works now, but man, what a nasty bug. I wish they would've
offered a patch for it, although I guess it's a moot point now that
newer versions of Access are out. Thanks again for the link Allen -
greatly appreciated!
 
Great news.

BTW, if you were bitten, you desperately need to apply the serivce packs for
Access 2000, and also for JET 4:
http://support.microsoft.com/sp/

You may have already done so now; if not, I consider it so important that we
put this information onto the Help | About screen of the applications we
write, so clients requesting support can tell us this stuff. Here's how:
Splash screen with version info
at:
http://allenbrowne.com/ser-53.html
 
Great news.

BTW, if you were bitten, you desperately need to apply the serivce packs for
Access 2000, and also for JET 4:
http://support.microsoft.com/sp/

You may have already done so now; if not, I consider it so important that we
put this information onto the Help | About screen of the applications we
write, so clients requesting support can tell us this stuff. Here's how:
Splash screen with version info
at:
http://allenbrowne.com/ser-53.html
Click to expand...

Thanks Allen. Everything was up to date on my computer, but I'm not
sure if that was the case on my co-worker's computer that I was
working on (I'm using a 10" LCD, he's using a 22" one, made it a
little easier on the eyes to take over his vacated desktop!). Will
this problem only occur if someone is trying to edit VBA code or forms
in design view in an older version of access? Or will this occur when
they open the database regardless of whether they are editing
information behind the constructed GUI I've made?
 
This particular bug only occurs when the VBA code is modified as described
in the kb article.

However, my recollection is that this was fixed in a very early service pack
for A2000, which implies your friend's machine lacks even these early SPs.
If so, there are so many other bugs (SP1 fixed 300+ in Access alone) that it
will be unreliable at best. I certainly would not develop on such a machine.
 
Back
Top