split database crashing on reports, set the printer

  • Thread starter Thread starter Janis
  • Start date Start date
J

Janis

I have a split front-end and back-end that crashes every time a report runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.
Gina suggested that I check the default printer is set because that could be
throwing it off. I will do that when I go to the office Monday but my
question is since this has been happening for some time shouldn't I do Allen
Brown's Quick Recovery to compact, decompile and recompile just to make sure?
I don't know if I should do it on both files or only the front-end where the
code is? Or if setting the printer seems to fix all crashing in that case I
don't need to do the recovery?
thanks,
 
On Sun, 15 Mar 2009 08:43:00 -0700, Janis

The point of decompile is: throw away all compiled VBA and get a new
compilation next time the program is used. Since there is only VBA in
the FE, only it should get this treatment.

-Tom.
Microsoft Access MVP
 
Janis said:
I have a split front-end and back-end that crashes every time a report
runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.
Gina suggested that I check the default printer is set because that could
be
throwing it off. I will do that when I go to the office Monday but my
question is since this has been happening for some time shouldn't I do
Allen
Brown's Quick Recovery to compact, decompile and recompile just to make
sure?
I don't know if I should do it on both files or only the front-end where
the
code is? Or if setting the printer seems to fix all crashing in that case
I
don't need to do the recovery?
thanks,
Click to expand...
 
Back
Top