MS Access and VBA Error

Diahann · June 11th, 2003, 01:25 PM

I am trying to open a form in MS Access 2000 with some record navigation vba code embedded. The error I am receiving is "Error accessing file. Network connection may have been lost." The file is however not on the network it is on my own hard drive so this could not be the error. Has anyone encountered and conquered or dodged this problem? Any help is much appreciated.

SerranoG · June 11th, 2003, 02:53 PM

Quote:

quote:Originally posted by Diahann
The error I am receiving is "Error accessing file. Network connection may have been lost." The file is however not on the network it is on my own hard drive so this could not be the error.

My first guess is that although your form is stored locally, it has a control source to some linked table. The linked table is on a database that is on the network. Did you check the form's control source? Is the table it wants local or on the network? Is the form based on a query that has a linked table in it?

Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

Diahann · June 13th, 2003, 07:46 AM

That would be the logical answer, but, everything is on my c drive with all the required tables in the one database with the form, which makes this one of the strangest things I have seen recently.

D...

yodajun · August 14th, 2003, 05:18 AM

I got the same error code, first in Excel when i using vbaunit, and next in word and access. Only visio has no error.
The cause is that, when i open a file in office 2000, not all of the reference files, such as msforms and vbide, get properly ready for use.
When i count the references in initial proc such as thisworkbook_open, the count amounts 4. but it amounts 6, when i submit count proc by hand after i opened the file.
Now, after i open the file, i am always forced to submit by hand a proc that removes MSForms and adds it again to restore references.
I hope this error may already have been fixed in office xp.
Junichi Yoda [email protected]

Junichi Yoda

Beth · April 9th, 2004, 06:56 AM

Did you get an answer to your problem as I have exactly the same problem and need an answer!

sal · April 9th, 2004, 08:47 AM

Stop.
Save your data to the c drive.

Your database may habe been corrupted. Do a search on this forum fot the error. You will find more info there.

Access can not find the vb extension file. You will have to create a new database and import all objects to that database.

Sal

SerranoG · April 9th, 2004, 09:15 AM

Have you looked at your linked table manager to make sure any linked tables have been redirected to your C: drive? There may be one or more still trying to point to the network.

Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

sal · April 11th, 2004, 07:55 PM

Serrano, this is a Access 2000 known bug. I am not sure if it was ever fixed with a service release.

It has gotten me before.

Sal

Pei · December 13th, 2004, 05:28 AM

Hi,
here is the link to th bug described by Sal:
http://support.microsoft.com/kb/840652

Could somebody tell me if it solves the problem ?

th

Pei

Loralee · January 2nd, 2005, 12:58 AM

We're using A2k and recently got lost 3 .mdb's with this message in the span of 8 days- (We call it the Wednesday curse). The KB article discusses this message coming up in Powerpoint- I didn't see anything about it addressed relating to Access. Did I miss something?

Does anyone know if it is "safe" to export some of the objects (such as tables) from the dead .mdb to reuse in another .mdb?

Thanks,
Loralee