[AccessD] VBA project corruption

Steve - I had a form that wasn't corrupted, but didn't work correctly at
all.  

Once I figured out which form it was, I commented ALL the code, did a
compact/repair, shutdown, reopened using /decompile, then recompiled from
the VBA window.

Then I decommented all the code in that form, and went through the same
routine.  

Then the form worked correctly without my having to rewrite anything.  My
guess was that commenting out all the code erased the p-code for that form,
then when I decommented my code, the p-code was re-created correctly. 

Anyway, it all took about 5 minutes and I was back in business.

Dan Waters


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant
Sent: Wednesday, July 05, 2006 9:13 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] VBA project corruption

A nice, long productive holiday weekend working on my Access 2000 mdb...
Then yesterday I open the file and get "The Visual Basic for
Applications in this project is corrupt."  Sigh.

I can shift bypass in to see objects.  But completely unable to run
anything with code, nor can I even view code.  Ran Repair and Compact to
no avail.  

Normally in these situations, I start a new MDB, then import all objects
from the corrupt DB.  But here, even the import function fails (same
error message) when I point it to the corrupt db.

I have heard of (but never used) third party utilities that work some
magic.  Any advice?  I'd love not to have lost many hours of work.

Thank you.

Steve Capistrant
Symphony Information Services
scapistrant at symphonyinfo.com
www.symphonyinfo.com
Office, Twin Cities: 763-391-7400, ext. 801. 
Office, Toll free: 888-357-1373, ext. 801
Direct: 612-237-0075
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com