VBA Error: "Error accessing file..."

[Guest]

Every so often, when I do an action that accesses code I wrote (e.g. push a
button...), I get a popup in Access. The title bar says "Microsoft Visual
Basic" and the message is: ""Error accessing file. Network connection may
have been lost."

All fine and dandy except I am running the database from my local machine.

Does anyone have any idea what is going on?

 

[Dirk Goldgar]

Every so often, when I do an action that accesses code I wrote (e.g.
push a button...), I get a popup in Access. The title bar says
"Microsoft Visual Basic" and the message is: ""Error accessing file.
Network connection may have been lost."

All fine and dandy except I am running the database from my local
machine.

Does anyone have any idea what is going on?

Are you using Access 2000? If so, see this KB article describing the
nasty bug that may have bitten you:

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

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.

 

[Guest]

Many thanks...I did not even realize that my Access here at work was so old!

Every so often, when I do an action that accesses code I wrote (e.g.
push a button...), I get a popup in Access. The title bar says
"Microsoft Visual Basic" and the message is: ""Error accessing file.
Network connection may have been lost."

All fine and dandy except I am running the database from my local
machine.

Does anyone have any idea what is going on?

Are you using Access 2000? If so, see this KB article describing the
nasty bug that may have bitten you:

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

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.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)