[AccessD] OT Favour trying a URL for me

Robin (Merseybeat) robin.lawrence at merseybeat.co.uk
Tue May 6 08:07:02 CDT 2008


Hi Andy,
Works fine for me - text follows if you're desparate...
Rgds
Robin

You receive an error message when you try to view the code in a module,
compile a database, create an MDE file or execute code in Access 2000
View products that this article applies to.
Article ID : 304548 
Last Review : April 7, 2006 
Revision : 7.0 
This article was previously published under Q304548
Moderate: Requires basic macro, coding, and interoperability skills. 

This article applies to a Microsoft Access database (.mdb) and to a
Microsoft Access project (.adp). 


On This Page

SYMPTOMS

CAUSE

RESOLUTION

Using Access 2000

STATUS

MORE INFORMATION

Steps to Reproduce the Behavior
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. 
Back to the top

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. 
Back to the top

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: 1. Open a form or a report in Design view. 
2. Save the code behind the form or the report as a text file. 
3. Set the form or the HasModule property of the report to No, and then save
the object. 
4. Repeat step 1 through step 3 for each form and report in the database. 
5. Save each module as a text file. 
6. Create a new blank database. 
7. 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. 
8. Restore the code behind each form and each report from the text files
that you created in step 1 through step 4. 
9. 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.


Back to the top

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 (http://support.microsoft.com/kb/276367/EN-US/) 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 (http://support.microsoft.com/kb/245025/) OFF2000: How to Obtain and
Install the Microsoft Office 2000 SR-1/SR-1a Update 
Method 2

1. 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.  
2. Before closing the database, open the Visual Basic Editor by pressing
ALT+F11. 
3. On the Debug menu, click Compile <database name>. 
4. 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.  

Back to the top

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article. 
Back to the top

MORE INFORMATION
Some of the programs that include Vbe6.dll version 6.3.91.8 are Microsoft
Office XP, its component applications, and Microsoft Visio 2002. The version
number of Vbe6.dll may also appear as 6.03.9180, depending on the version of
Windows that you are using. 
Back to the top

Steps to Reproduce the Behavior
1. On a computer that has both Microsoft Access 2000 and version 6.3.91.8 of
the Vbe6.dll installed, open Microsoft Access 2000. 
2. In Microsoft Access 2000, create a new blank database and name it
ImportTest.mdb. 
3. On the File menu, point to Get External Data, and then click Import. 
4. Browse to the sample database Northwind.mdb for Microsoft Access 2000.  
5. In the Import Objects dialog box, click the Modules tab. 
6. Click the Startup module, and then click OK.  
7. After successfully importing the Startup module, close the ImportTest
database. 
8. In Microsoft Access 2000, open the ImportTest database. 
9. Open the Startup module in Design view. Note that you receive one of the
error messages that is mentioned in the "Symptoms" section of this article,
and you are then unable to view the code for the Startup module. 

Back to the top


----------------------------------------------------------------------------
----

APPLIES TO
. Microsoft Access 2000 Standard Edition 

Back to the top

Keywords:  kbqfe kbhotfixserver kbprogramming kbbug kberrmsg KB304548 

Back to the top

 

Provide feedback on this article
Did this article help you solve your problem?
 Yes 
 
 No 
 
 Partially 
 
 I do not know yet 
 

 Strongly Agree        Strongly Disagree 
 
 9 8 7 6 5 4 3 2 1 
The article is easy to understand          
The article is accurate          

Additional Comments:
To protect your privacy, do not include contact information 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
Sent: 06 May 2008 13:58
To: Access Developers discussion and problem solving
Subject: [AccessD] OT Favour trying a URL for me


Can someone do me a favour and try this link

http://support.microsoft.com/?kbid=304548

I'm at work and getting no response at all from anything at
http://support.microsoft.com

I'd like to know whether MS have a problem or me.

--
Andy Lacey
http://www.minstersystems.co.uk



________________________________________________
Message sent using UebiMiau 2.7.2

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com






More information about the AccessD mailing list