Liz Doering
ldoering at symphonyinfo.com
Wed Jul 5 17:02:30 CDT 2006
>From you, Andy, that means a lot. Thank you.
Liz
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
Sent: Wednesday, July 05, 2006 5:00 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] VBA project corruption
Nice work Liz.
-- Andy Lacey
http://www.minstersystems.co.uk
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Liz Doering
> Sent: 05 July 2006 22:28
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] VBA project corruption
>
>
> Andy, Bill, William and Dan,
>
> Steve handed this issue off to me--being the boss has some
> advantages--for him! :)
>
> Turns out, this is a .dll problem, not an actual object
> corruption problem. Microsoft explains it all here:
> http://support.microsoft.com/?scid=kb;EN-US;304548.
>
> I didn't like the solutions they offered, which included
> exporting objects to text files and reimporting them. There
> are nearly 900 forms, reports and modules in this .mdb!
> Using the advice from
> http://www.granite.ab.ca/access/decompile.htm, I made a .bat
> file to decompile with 2003, ("C:\Program Files\Microsoft
> Office\OFFICE11\MSAccess.exe" /decompile). Once the decompile had run
> (a long time), I saved the file to 2003 format and all was well.
>
> I imagine that this is because 2003 is playing nicely with
> version 6.3.91.8 of the Vbe6.dll file, unlike 2000. But I
> don't understand why just opening the thing in 2003 didn't
> have the same effect.
>
> Thanks for all your help!
>
>
>
> Liz Doering
> Symphony Information Services
> ldoering at symphonyinfo.com
> www.symphonyinfo.com
> 763-391-7400 x802
>
>
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Steve Capistrant
> Sent: Wednesday, July 05, 2006 10:01 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
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com