J
James Carpenter
I'm seeking advice on an Access 2002 database with VBA code which will not
open in Access 2003. The database was operating successfully under Access
2002, and was compacted and repaired before the 2003 upgrade was installed.
It is a single-user database still under development; there are several
backup copies, all displaying these symptoms.
The database has an autostart form which displays a few seconds, then closes
and launches the main switchboard. Launching in 2003 generates the Microsoft
Visual Basic message while the form displays: "An error occurred while
loading 'Report_R_Agg_S_I'. Do you want to continue loading the project?"
This refers to an empty class module.
Clicking "no" produces the message "The VBA project in the database is
corrupt."
Clicking "yes" gives the message "Invalid procedure call or argument" and
opens the debugger to a module that isn't running at this point.
Opening the database with the shift key down bypasses the autostart form,
but then opening the VBA code produces the same sequence of errors.
Converting the database isn't possible because it is already in 2002-2003
format. Compact and repair under 2003 generates the same sequence of error
messages and fails.
Has anyone experienced similar problems? If so, how were they resolved?
Sorry so wordy; just trying to describe the situation as completely as I can.
Thanks to anyone who can offer help!
open in Access 2003. The database was operating successfully under Access
2002, and was compacted and repaired before the 2003 upgrade was installed.
It is a single-user database still under development; there are several
backup copies, all displaying these symptoms.
The database has an autostart form which displays a few seconds, then closes
and launches the main switchboard. Launching in 2003 generates the Microsoft
Visual Basic message while the form displays: "An error occurred while
loading 'Report_R_Agg_S_I'. Do you want to continue loading the project?"
This refers to an empty class module.
Clicking "no" produces the message "The VBA project in the database is
corrupt."
Clicking "yes" gives the message "Invalid procedure call or argument" and
opens the debugger to a module that isn't running at this point.
Opening the database with the shift key down bypasses the autostart form,
but then opening the VBA code produces the same sequence of errors.
Converting the database isn't possible because it is already in 2002-2003
format. Compact and repair under 2003 generates the same sequence of error
messages and fails.
Has anyone experienced similar problems? If so, how were they resolved?
Sorry so wordy; just trying to describe the situation as completely as I can.
Thanks to anyone who can offer help!