ACC: Sent Keys Lost If Microsoft Access Yields ProcessorID: Q109958
|
Novice: Requires knowledge of the user interface on single-user computers.
If you use the SendKeys statement in Access Basic to fill a dialog box and
Microsoft Access yields the computer's processor to another Windows process
before the dialog box appears, the sent characters will be lost.
One situation where this might occur would be filling a report name in the
Print dialog box when you are printing a report to a file.
To minimize the chance of losing sent keys, make your queries as short as
possible. When a query takes a long time to run, Windows has more time to
interrupt the task to serve another Windows process. By shortening your
queries, you give Windows less time to interrupt.
If this problem occurs when you are printing to a file, try printing
directly to the file through your printer driver. If your printer driver
supports this, set it to print your report directly to a file instead of
using Microsoft Access to do this.
Microsoft has confirmed this to be a problem in Microsoft Access versions 1.0, 1.1, and 2.0. This problem no longer occurs in Microsoft Access version 7.0.
SendKeys
Keystrokes: text.txt
Wait: No
SendKeys
Keystrokes: {enter}
Wait: No
OpenReport
Report: Employee Sales By Country
Mode: Print
For information on setting up a printer in Windows 95, search for "Printer,
setting up a printer" using the Windows 95 Help menu.
For more information about setting up a printer, search for "SendKeys
action" or "printing, Print dialog box options" using the Microsoft Access
2.0 Help menu.
For more information about setting up a printer, search for "Print Setup"
or "Sendkeys" using the Microsoft Access 2.0 Help menu.
For more information about setting up a printer in Microsoft Windows 3.x,
press F1 while in the Printer Setup window.
Additional query words: programming timeout
Keywords : kbprint PtrOthr
Version : 1.0 1.1 2.0
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: April 2, 1999