Access 97 db gives compile when run error under Access XP

[Jim]

Hi there,

I've got an Access 97 database that I don't want to convert to XP, and
had been running under Access XP on a winXP pro box quite successfully
for many months now, but recently seems to have broken.

Virtually anything I try to do with it in XP (open a form, a report, a
table, etc.) throws a "Compile Error" and brings me into the vba code
debugger where a good 2/3 of code from a module in the db is missing,
and thus causing an "expected end of statement error" (perfectly
logical since most of the code has vanished.)

When I open the batabase in Access 97, where it was created, the
module is intact and functions just fine, but under XP, most of it's
code is just gone!

I cannot figure out what has caused XP to no longer see all the code
that is storred in the module. I recently installed an application
that required .net framework and installed that on my machine. Can't
recall if I'd even run database successfully after that or not, but
thought I'd mention since it was about the only recent change I could
think of.

Any suggestions?

Thanks,
Jim

 

[John Nurick]

Hi Jim,

I've never heard of this before. Do things get any better when you open
a copy of the database in Access 97 and repair and compact it and then
compile all modules before opening it in 2002?

 

[Jim]

Hi John,

Thanks for the repair, compact, compile suggestion. It seemed to do
the trick, however it did throw me a small curve that I found weird.
Upon opening it in Access XP for the first time after repairing, I was
presented with the standard "Open/Convert" dialog box, but when I
choose "open" and clicked OK, it would loop back around to the
"Open/Convert" dialog again. It was endless when trying to choose
"open", but after clicking cancel instead, the database did open and
seems ok for now.

Thanks again!
Jim