>Sorry, Nigel, but now I'm really confused.
>
>You have an application that has a data entry (?) form. This form is modeless, and has a button that issues a REPORT FORM command and sets focus...where? Why? If the button is on the form, and has focus enough to issue a set focus command to it's parent form, then the parent form already has focus, doesn't it?
>
>Admittedly I don't handle my reporting like this, but the set focus seems really odd. What happens if you just do the REPORT FORM w/o a set focus (just for jollies)?
>
>Also, what did you mean in your original message about having to restart the program after printing? Does the form close? Does the APP quit? Does this happen both from the command window and from running the EXE directly (if there is one)?
>
>Where is your READ EVENTS? Where is your CLEAR EVENTS?
>
>You specifically mention that you have 9 buttons and 3 of them print reports. Was that important? Do some of the print buttons work okay? What do the other six buttons do?
>
>You'll probably already have solved your problem, and I might be chasing a red herring
>
>PS you need an ON SHUTDOWN routine to close your app with the "X"
>
>...snip
>>To answer Nancy's questions first the form is modeless, its in
>>an application and that was all the code in the command button
>>except for a setfocus to the form.
>>
>...snip
>>
>>the message says "Cannot quit Fox Pro but when you click OK
>...snip
Nancy,
As Derek said, my message was in reply to his original. The only reason I put setfocus is to take the focus off of the "Print" button so that the operator cannot "accidentally" hit enter and trigger the report again. It is not there to solve any problems - apparently it does???
