Macro Operations Cause Access '03 to Crash.

  • Thread starter Thread starter TWYSTD
  • Start date Start date
T

TWYSTD

In attempting to revise an database to pull info from a new year, and since I
still need to be able to pull the current year, I've been duplicating
queries, changing the search criteria, and, obviously, changing the names of
the queries. In order to automate the process, I've been performing similar
operations with my macros.
After making the required changes to the macros, I attempt to save, and
Access crashes. This occurs whether I create a macro from scratch or copy
and "save-as" them under different names.
The original database was built under Access 2000. At one point, I
attempted to create an .mde, so my users couldn't make unwanted changes and I
could do maintenance while allowing users to continue their operations.
However, what resulted was a replicated database, which was subsequently
converted back to the "mother" database (or at least so I thought), but all
of the queries, macros, etc still have the replicated icons.
Out of all of this, I would appreciate any insights as to why I can't save
corrected or copied macros.

Thanks,
 
TWYSTD,

First thing to do here, I would say, is make a brand new MDB file, and using
the File=>Get External Data=>Import menu, import all database objects from
your existing file.

Then, Compact & Repair, and, if there is any VBA code within the
application, compile the project.

After that, try your macros again.
 
Steve,

Thanks for the feedback. I'll definitely attempt your solution. Any idea
why I can't duplicate a macro in the existing mdb? I have been able to do it
in the past.
 
Steve Schapel said:
TWYSTD,

First thing to do here, I would say, is make a brand new MDB file, and using
the File=>Get External Data=>Import menu, import all database objects from
your existing file.

Then, Compact & Repair, and, if there is any VBA code within the
application, compile the project.

After that, try your macros again.
Click to expand...
 
TWYSTD,

Well, the hypothesis behind my suggestion is that your database has been
screwed around with so much that it's in so much of a mess that some stuff
has stopped working properly. So let's start with a clean slate, and see if
that helps.
 
Back
Top