Corruption of VBA code in MDB (2002).

[Kraeg]

I've tried Compact/Repair, JetComp, and several other methods, but this MDB just won't repair.
I can get to Forms, reports, Queries, Macros... but not to Modules (including those behind Forms and Reports).
Are there any ways to repair VBA code? Or perhaps extract it?

I have an MDE of this MDB, so there's been no down time..... but if I have to rebuild the MDE, I need to get it repaired (all I did was change one line of code and it went corrupt.... I should have backed it up before changing anything).

 

[katho]

you might try to downgrade the mdb into a prior version (save a 2000 version as 97). You might also try to use Visual Basic (or even another access db) to import the modules that were corrupted.

Can you keep me posted on the result ?
Good luck!

 

[Kraeg]

I had tried importing/exporting, converting to previous versions.... nothing worked. It's really corrupt (and all I did was add a line of code and save).

What I ended up doing was using an older version from home.... it was basically the same (just had to add a function to the "Default" properties of some text boxes in some Forms).

What a nightmare. But I have learnt; before doing ANY changes, I'll backup the source file I am about to work on.

 

[Stamey]

There's an undocumented switch called /decompile which may help. See this page for more info:

http://www.trigeminal.com/usenet/usenet004.asp?1033

Chris

 

[Kraeg]

I had tried /decompile too.

But thanks (that link has some interesting info, and I may have not used /decompile correctly..... in fact, I believe I used /decomiple, added a line of code, saved, and then got the corruption (Access froze during the save)).