Arrrggghhh!!! Corrupt VBA Project....??? 2

[mike777]

Have you ever had this happen to you??:
You spend three weeks developing a program, and then you go to open the mdb one day and get the following error message:
Microsoft Visual Basic
Error accessing the file. Network connection may have been lost.
You hit "OK", and it keeps popping up about 10 times. Finally, the last error message says,
File format no longer supported., and all your code is gone, or mysteriously inaccessible.
Does anyone know what this is all about? I can restore the file from backup, of course, but I will lose about a day's work.
Do you think this is an Access problem (like maybe there were too many lines of code in this module??), or do you think it is a system problem (corrupt data, maybe, but we didn't have any problems anywhere else...). All of the table data, queries, etc. in the mdb are accessible and work fine; it's just the VBA that is whacked.
Any help you can provide will be very much appreciated.
Thanking you in advance.
-Mike

 

[mike777]

Incidentally, I just determined that there are 559 lines of code in this module. Thanks.

 

[VBslammer]

This is a documented bug in the VBE6.dll and I have had numerous headaches because of it. Here is an article about it:

Microsoft Knowledge Base Article - Q304548

One thing I have found is that importing objects into my Access 2000 database using 'File -> Get External Data -> Import' will cause this error - which is unrecoverable. If I need to bring an object from another database, I open both databases and copy-paste the object from one into the other.

Another thing I am careful about is making sure I compile my project before I close it. This ensures I don't have any syntax errors when I close the database.

I also installed Roxio's Go Back software specifically to combat this problem. It allows me to 'Roll Back' my system to any number of 'Safe Points' before the database became corrupted.

When you program Access, you're gonna CRASH sooner or later, especially if you're like me and you like to use the debugger for 'Edit -n- Step' troubleshooting, a sure way to cause memory leaks!

Good Luck

VBSlammer

 

[mike777]

Right on!! Hit the target...thanks!