wvmitchell
Programmer
- Nov 27, 2001
- 4
When you select a report from the custom menu, the report Open event opens a modal popup form where the user selects the criteria and group/sort expression, then clicks OK to preview the report with those settings. The report Close event closes the popup form. Simple enough, you would think.
On three out of about 15 PC's, as you click to view successive pages, from page 7 & up (of 22 pages) the report is blank. After you view the blank pages, you can still navigate forwards & backwards thru the report, and zoom in and out, but - Access stops responding to the close button (top right corner) on the report window. If you click the close button on the main Access window, it displays error 2486:
"You can't carry out this action at the present time. You tried to run a macro or used the DoCmd object in Visual Basic to carry out an action. However, Microsoft Access is performing another activity that prevents this action from being carried out now."
Clicking Debug on the error message highlights the DoCmd.Close "name of the modal popup form" in the report Close event. This same logic is used on dozens of other reports, and they work just fine.
The three "bad" machines are: Win95, no SR-1; Win98, no SR-1; Win98, with SR-1 installed. They all connect to the same network printer. A fourth machine using the same printer works OK.
On three out of about 15 PC's, as you click to view successive pages, from page 7 & up (of 22 pages) the report is blank. After you view the blank pages, you can still navigate forwards & backwards thru the report, and zoom in and out, but - Access stops responding to the close button (top right corner) on the report window. If you click the close button on the main Access window, it displays error 2486:
"You can't carry out this action at the present time. You tried to run a macro or used the DoCmd object in Visual Basic to carry out an action. However, Microsoft Access is performing another activity that prevents this action from being carried out now."
Clicking Debug on the error message highlights the DoCmd.Close "name of the modal popup form" in the report Close event. This same logic is used on dozens of other reports, and they work just fine.
The three "bad" machines are: Win95, no SR-1; Win98, no SR-1; Win98, with SR-1 installed. They all connect to the same network printer. A fourth machine using the same printer works OK.