Access 2003 shuts down on report over one page

  • Thread starter Thread starter breauxlg
  • Start date Start date
B

breauxlg

I have a report that will run just fine if it doesn't generate over one page
on output, but if it goes to a second page, Access says it has to close and
apologizes for the inconvienience, etc. It seems to be a memory problem, but
I have 2 gig of real memory and 4 gig of virtual memory. I know there is a
hotfix for office svc pack 3 and I tried it. It seems to work in one location
but not in another. In addition to this problem I have a report that runs
just fine, but if I try to modify it in design view, the save either hangs or
closes Access as above. Anybody know of a fix???
 
Before you start any intense recovery efforts, make a copy of your
application...

Force a compile of your application if you can.

Compact and repair your application if you can.

If no success yet,then google these Access newsgroups for "decompile"
to find examples of command lines to decompile your application.

If all of that still leaves you with a broken application then fall
back to your last backup. If you are working with a FE/BE (split)
configuration then your data is probably safe.

If you don't already have an automatic backup process in the works you
should consider creating or getting one.

There are also commercial Access recovery products available.

HTH
 
I have decompiled, compacted, repaired, recompiled and the problem will still
come up on some PC's. I can take the same database, move it to another pc and
not have the problem. The references are all the same, the products are all
at the same level (all updates from microsoft update plus any hotfixes
available) and the problem is not consistent.
 
You might try Repairing the Office installation on one of the problem
PCs and try it again. May even try removing Office completely,
rebooting and reinstalling it. First be sure that you have everything
you need to reinstall.

The thing is that you know it's somehow a matter of configuration that
varies by PC. Have you enabled "Break on all Errors" in your options?
Using that you may be able to flush out other differences between the
systems.

If I were at the point where you are I'd be considering a call to
Microsoft Support. Their participation can be expensive but so is
flailing around with a flaky application that your users can't trust.

If ever you do get a solution, please post it for the benefit of
others.

HTH
 
Back
Top