Network Error - corrupted code behind form Access 2000 
Author Message
 Network Error - corrupted code behind form Access 2000

Know problem, if you have some OfficeXP apps installed.
Check out this Microsoft KB Article

http://www.*-*-*.com/ ;en-
us;304548

Quote:
>-----Original Message-----
>Over the past 2 years our staff has encountered a
problem
>when running Access 2000.  The mdb becomes corrupted,
and
>we get a message "Error Accessing File - Network
>Connection May Have Been Lost" when trying to open code
>behind a form, or in some cases when opening the form
>itself (could be related to an OnOpen event).  We have
>also seen this error come up with Modules.  In that
case,
>ALL the VB code in the project became corrupted, and
>inaccessible.  In all cases the file is on the local C:
>drive, so the Network Connection message is inaccurate.

>This has occurred while running under Win 2000 and Win
XP,
>and usually with the latest in patches in place.  It
>occured on various PCs as well.  We estimate it has
>happened with about 5 databases, over 3 PCs, and under
>various OS versions.  Once the mdb is corrupted we
cannot
>get it back to normal by using Compact/Rebuild, by
>importing into a new mdb, or any other common tricks.

>To see an example of the error, load the attached mdb,
and
>click Done on the startup form.  Any ideas?



Thu, 28 Jul 2005 23:20:13 GMT  
 Network Error - corrupted code behind form Access 2000
This is the exact problem - and with your help we will now
make sure to upgrade to Office 2000 SP-3, should fix the
dll conflict.  Thanks!
Quote:
>-----Original Message-----
>Know problem, if you have some OfficeXP apps installed.
>Check out this Microsoft KB Article

>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;304548

>>-----Original Message-----
>>Over the past 2 years our staff has encountered a
>problem
>>when running Access 2000.  The mdb becomes corrupted,
>and
>>we get a message "Error Accessing File - Network
>>Connection May Have Been Lost" when trying to open code
>>behind a form, or in some cases when opening the form
>>itself (could be related to an OnOpen event).  We have
>>also seen this error come up with Modules.  In that
>case,
>>ALL the VB code in the project became corrupted, and
>>inaccessible.  In all cases the file is on the local C:
>>drive, so the Network Connection message is inaccurate.

>>This has occurred while running under Win 2000 and Win
>XP,
>>and usually with the latest in patches in place.  It
>>occured on various PCs as well.  We estimate it has
>>happened with about 5 databases, over 3 PCs, and under
>>various OS versions.  Once the mdb is corrupted we
>cannot
>>get it back to normal by using Compact/Rebuild, by
>>importing into a new mdb, or any other common tricks.

>>To see an example of the error, load the attached mdb,
>and
>>click Done on the startup form.  Any ideas?
>.



Sat, 30 Jul 2005 00:06:30 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Viewing Code Behind Forms: Unexpected Error

2. Code-behind file inheriting from another code-behind file

3. Importing an Access 2000 table into another Access 2000 database with VB Code

4. Access 2000 - VBA Help File Corrupted?

5. CORRUPT ACCESS 2000 DATABASE - URGENT!

6. using JRO compactdatabase method to repair corrupt access 2000 database

7. Database corrupts when use register locks whith access 2000 and vb6

8. Access 2000 database corrupting!

9. ADO with Access 2000 and corrupt strings

10. Error code 7874 vs. 3011 in Access 2000

11. Modify query using code behind forms

 

 
Powered by phpBB® Forum Software