[AccessD] VBA project corruption

Steve

...see http://www.granite.ab.ca/access/decompile.htm for detailed steps.

...and for A2K3 mdbs, Max Sherman's EatBloatV2 works much better than 
"decompile"

William

----- Original Message ----- 
From: "Dan Waters" <dwaters at usinternet.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Wednesday, July 05, 2006 11:02 AM
Subject: Re: [AccessD] VBA project corruption


> Steve,
>
> Try putting /decompile AFTER the path to your application.  It will be the
> last item in the command line or in the  target field of a shortcut.   I 
> set
> mine up that way and it does work.  Not sure if how I do it is the only 
> way
> though.
>
> Dan Waters
> ProMation Systems, Inc.
>
> -----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:51 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA project corruption
>
> Andy,
> I did try decompiling, using this syntax from a RUN window:
> [path and file for MSAssess.exe] /decompile [path and file for my mdb].
>
> Not sure if I constructed that correctly.  But it appeared to chug along
> and do something, but then ended up with the same VBA Corrupt message.
>
> Steve
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
> Sent: Wednesday, July 05, 2006 9:31 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA project corruption
>
> Steve, have you tried decompiling?
> --
> Andy Lacey
> http://www.minstersystems.co.uk
>
>
> --------- Original Message --------
> From: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Subject: [AccessD] VBA project corruption
> Date: 05/07/06 14:15
>
>
> 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
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>