Hi MarkD,
SYMPTOMS
When you try to view the code for a module, try to compile a database, try
to create an MDE file, or try to execute code in a Microsoft Access 2000
database, you may receive one of the following error messages:
Error accessing file. Network connection may have been lost.
-or-
This action will reset the current code in break mode.
CAUSE
You may receive one of these error messages when both Microsoft Access 2000
and version 6.3.91.8 of the Vbe6.dll file are installed on the computer,
and either of the following conditions is true:
You imported forms or reports that contain code modules or standalone
modules into a new Microsoft Access 2000 database by using Microsoft Access
2000.
You copied and pasted forms or reports that contain code modules or
standalone modules into the Microsoft Access 2000 database by using
Microsoft Access 2000.
Then, you close and reopen the database and try to view, execute, or
compile the code.
RESOLUTION
If you have a computer without the version of Vbe6.dll that is mentioned in
the "Cause" section, you may be able to repair the problem with the
following steps:
Open a form or a report in Design view.
Save the code behind the form or the report as a text file.
Set the form or the HasModule property of the report to No, and then save
the object.
Repeat step 1 through step 3 for each form and report in the database.
Save each module as a text file.
Create a new blank database.
On the File menu, point to Get External Data, and then click Import. Import
all tables, queries, forms, reports, data access pages, and macros to the
new database.
Restore the code behind each form and each report from the text files that
you created in step 1 through step 4.
Import each text file that you saved in step 5 as a new module.
If you do not have a computer without the version of Vbe6.dll mentioned in
the "Cause" section, you must revert to a known good backup copy of the
database. To prevent this problem from happening again, use one of the
following methods, depending on which version of Access you are using.
Using Access 2000
Method 1
To prevent this problem from happening again, obtain the latest service
pack for Microsoft Office 2000. You must install this service pack on all
computers that run Office 2000.
For additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack
IMPORTANT: Before you install Microsoft Office 2000 Service Pack 3 (SP-3),
you must have Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a)
installed first.
For additional information about how to obtain Office 2000 Service Release
1/1a (SR-1/SR-1a), click the following article number to view the article
in the Microsoft Knowledge Base:
245025 OFF2000: How to Obtain and Install Microsoft Office 2000 Service
Release 1/1a (SR-1/SR-1a)
Method 2
When you import to a new database, create a new database and import the
objects into the new database. Or, when you copy objects in the current
database, copy and paste the objects into the current database.
Before closing the database, open the Visual Basic Editor by pressing
ALT+F11.
On the Debug menu, click Compile <database name>.
After you compile the database, close and save the database. Note that when
you reopen the database and view the code, the error message that is
mentioned in the "Symptoms" section of this article does not occur.
For Further Information : Microsoft Knowledge Base Article - 304548
Please let me know has this helped You...
Thank you...
Raghu...
This posting is provided "AS IS" with no warranties, and confers no rights.
