Karen, try just printing to screen. The screen display allows a print, or [Esc] to drop out of the print dialog.
PRINT rptname WHERE ... OPTION SCREEN | WINDOW_STATE MAXIMIZED
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Emmitt:
I too will be eagerly waiting for an answer to this. For a 7.1 Windows App, I tried to do what I had done in the older DOS app, put up a Pause box that says "click OK to begin printing, or press [ESC] or [X] to stop printing". It might work correctly a time or two, but I can't figure out why sometimes it won't work until you exit and come back in. Had to replace the Pauses with a yes/no dialog.
Karen
My function returns the date selected and an integer - either 1 or 0 -
indicating whether [Esc] was pressed. Problem is it erroneously returns 0,
indicating [Esc], when [Esc] was not pressed. This can happen when a PAUSE
was executed just prior to the SP call and the user pressed [Esc]
then. What I need to do is tell R:Base to fageddabout the previous
keystroke and correctly report what just happened, which may be one or more
mouseclicks only.
Albert Berry
Management Consultant
RR2 - 1252 Ponderosa Drive
Sparwood BC, V0B 2G2
Canada
(250) 425-5806
(250) 425-7259
(708) 575-3952 (fax)
[EMAIL PROTECTED]
