E
Eric Flamm
I have developed an application in Access 2002 using
Access 2000 format. The back-end has about a dozen
tables, and the front-end is a few queries and reports.
The reports use DSUM and DCOUNT, but seem to function
well in Access 2002. When I load the front-end in Access
2000, all goes fine, including the simpler reports. But
when I run the more complex report, it stalls, with the
status line reading "Formatting page. Press ctrl-break to
stop...". Even after 20 minutes, ctrl-break takes me back
to report design view. I even tried deleting ALL of the
controls from the report (but left it bound to the source
query) and it still died. But when I built a similar
request directly in Access 2000, it seems to work OK. Do
I have to develop all of my reports in Access 2000? What
will happen if somebody comes along and runs them from
Access 2002 or 2003?
It's been suggested this might be a printer driver issue
(different drivers on the 2 PCs), but that doesn't seem
very likely, does it? I'll try some of Tony's performance
improvers - maybe that Always Open table will do the
trick - but I'd appreciate any insight you all have on
this problem.
Thanks,
Eric
Access 2000 format. The back-end has about a dozen
tables, and the front-end is a few queries and reports.
The reports use DSUM and DCOUNT, but seem to function
well in Access 2002. When I load the front-end in Access
2000, all goes fine, including the simpler reports. But
when I run the more complex report, it stalls, with the
status line reading "Formatting page. Press ctrl-break to
stop...". Even after 20 minutes, ctrl-break takes me back
to report design view. I even tried deleting ALL of the
controls from the report (but left it bound to the source
query) and it still died. But when I built a similar
request directly in Access 2000, it seems to work OK. Do
I have to develop all of my reports in Access 2000? What
will happen if somebody comes along and runs them from
Access 2002 or 2003?
It's been suggested this might be a printer driver issue
(different drivers on the 2 PCs), but that doesn't seem
very likely, does it? I'll try some of Tony's performance
improvers - maybe that Always Open table will do the
trick - but I'd appreciate any insight you all have on
this problem.
Thanks,
Eric