Access 2000 and Visual basic for Applications problem

[Mitsch]

I have a MS Access 2000 project that I designed about 7 years ago. I am
currently using Access XP. I tried to open my Access 2000 project and
received the following error "The visual basic for Applications progject in
the database is corrupt". I tried to compact and repair the database, but an
error comes up that one of my reports is corrupt. The file doesn't open
after I tried to repair. I urgently need this file. I was able to import
the tables and querries into a new database, but the forms do not import
because of the VBA error. Any suggestions?

 

[Larry Linson]

An Access 2000 database should open, in run mode, and in design view, in
Access 2002 (that's the Access in Office XP). Do you have all the Service
Packs and hotfixes applied to Access 2002? Have you tried opening it in
Access 2000, opening a module window, and doing a compilation -- does it
execute properly under any version of Access? When you say "Access project"
that could be a generic description of an Access database, or it could have
the specific meaning of an Access .ADP file -- if it is the latter, someone
else will have to help you... I worked with an .ADP a few years back, and
found no motivation to work with any other .ADPs.

Do you have a backup copy? What happens with that copy? If you do not have a
backup copy that was working when you backed it up, you have learned an
object lesson about the necessity of backups.

Does the database open in Access 2000? When you get the message about the
VBA project being corrupt, exactly what happens?

I have sometimes been able to manipulate objects in one database from
another (even one that is a different, later version). If you could change
the HasModule property of the problem form / report to "No", then you might
be able to import the forms and reports, and some of the VBA code.

Larry Linson
Microsoft Office Access MVP