David,
>
>
>I work from a different mindset here. My report control class has a optiongroup for destination (printer, screen, browse) and a Do Report button, so they select the report, enter and relevant subset criteria and hit the Do report button. More than 1/2 the time they are just viewing the reports without printing.
>
Usually the list of reports is around 5 or 6, and what mine do is preview one, and if it's OK, print all the rest. However, I do prefer the check boxes since I don't have to re-issue the query and I can loop through and determine output. I should mention that a standard practice of mine is to allow the user to send a printed report to a spreadsheet (COPY TO...TYPE WK1) (Yeah, we're Lotus).

>
>Maybe a DoEvents() call in one of the group or page band events might help?

Never thought of that one. I'll try it and see if it works. I'll let you know. Thanks, David.
>
>>Of course, if we had some control in this area, this wouldn't be aan issue.
>
>Agreed, we sure could use some more control, like having report events Top, Previous, Next, Bottom, GotoPage, Print, Exit and Cancel that get called when the preview buttons are pressed.

Sigh...Maybe in 7.0.:-)