Bill Patten
bill_Patten at earthlink.net
Wed Jul 5 14:15:35 CDT 2006
Steve, Try making several copies of the bad database, then in one of the copies start deleting forms one at a time and try compact and repair after each deletion. If it is a bad form it will finally allow you to compact and repair, when it does then go to another copy and just delete that form. If it compacts ok you now know which form. Then go to an other copy create a new form and import all the controls from the bad form and the deleted the bad form. If it compacts ok you now only have to rewrite the code in the one form and that should save you time. I had something similar once and it was a corrupted form and I was able to save all the other forms, etc. Hope this helps. Bill ----- Original Message ----- From: "Steve Capistrant" <scapistrant at symphonyinfo.com> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Wednesday, July 05, 2006 7:12 AM 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