G
Guest
I have a Access 2003 application with a SQL Server database that performs
intensive data processing for reports. Typically the application gets input
from the user and then launches the data processing and then opens the
report. I'm finding that if the user switches to another Windows task then
the Access process "gets lost". The process doesn't seem to finish properly
or the report opens with the dialog still visible. It's usually necessary to
kill the Access task and run it again.
This is common with several of my systems if the data processing is
extensive, it requires launching the report and then not toucing the machine
until it's done. Is this common? What's the solution?
intensive data processing for reports. Typically the application gets input
from the user and then launches the data processing and then opens the
report. I'm finding that if the user switches to another Windows task then
the Access process "gets lost". The process doesn't seem to finish properly
or the report opens with the dialog still visible. It's usually necessary to
kill the Access task and run it again.
This is common with several of my systems if the data processing is
extensive, it requires launching the report and then not toucing the machine
until it's done. Is this common? What's the solution?