Modules Corrupted

[terri]

I was given a 2003 database where all the vb code appears to have been
corrupted.

Trying to open any module results in a "module name "xxx" is mispelled"
error. None of the forms or reports appear in the VB Project tree --
although they open in design mode and show [Event Procdure] tags, there is no
code behind them. I cannot import or export anything that has vb code.
Repair and Compact had no affect.

Any chance that this can be fixed?

 

[John W. Vinson]

I was given a 2003 database where all the vb code appears to have been
corrupted.

Trying to open any module results in a "module name "xxx" is mispelled"
error. None of the forms or reports appear in the VB Project tree --
although they open in design mode and show [Event Procdure] tags, there is no
code behind them. I cannot import or export anything that has vb code.
Repair and Compact had no affect.

Any chance that this can be fixed?

Try creating a new, empty database and using File... Get External Data...
Import to import objects from this one. Import code-free objects first; then
import reports and forms, one by one, backing up first and testing compilation
after each import. Finally import your modules one by one, same drill.

See http://www.granite.ab.ca/access/corruptmdbs.com for some detailed
suggestions about recovery. Decompiling might help.

 

[terri]

Thanks for responding John.

I had already tried your suggestion. Importing (or exporting) throws up a
"Name conflicts with existing module..." message.
--
terri

I was given a 2003 database where all the vb code appears to have been
corrupted.

Trying to open any module results in a "module name "xxx" is mispelled"
error. None of the forms or reports appear in the VB Project tree --
although they open in design mode and show [Event Procdure] tags, there is no
code behind them. I cannot import or export anything that has vb code.
Repair and Compact had no affect.

Any chance that this can be fixed?

Try creating a new, empty database and using File... Get External Data...
Import to import objects from this one. Import code-free objects first; then
import reports and forms, one by one, backing up first and testing compilation
after each import. Finally import your modules one by one, same drill.

See http://www.granite.ab.ca/access/corruptmdbs.com for some detailed
suggestions about recovery. Decompiling might help.