Corrupted VBA project

[Guest]

I had an mdb file created in Access 2002 SP(None); worked on in SP2; worked on again in SP(none); finally in SP2, where VBA project has become corrupt (according to Compact/Repair tools) - get repeated "Id is not an index in this table" error message whenever accessing an object, and can't view modules at all. "JetComp" utility can't recover either. Has anyone had similar problem?

 

[Dirk Goldgar]

I had an mdb file created in Access 2002 SP(None); worked on in SP2;
worked on again in SP(none); finally in SP2, where VBA project has
become corrupt (according to Compact/Repair tools) - get repeated "Id
is not an index in this table" error message whenever accessing an
object, and can't view modules at all. "JetComp" utility can't
recover either. Has anyone had similar problem?

Have you tried decompiling a copy of this database? There's a
barely-documented /decompile command-line switch, with a syntax like
this:

msaccess.exe /decompile "C:\Path To\YourDB.mdb"

Do this only to a *copy* of your database, as it has on rare occasions
been known to make things worse.

 

[ali kwok]

Thanks very much for your reply Dirk, it was more than I
expected - I'll try your suggestion and post what happens.

Ali