Thanks, Derek and Nigel, for helping me get back on track, I hope :-)
>To answer your questions as to what my program looks like; it
>consistes of a main program with just read events and then on
>shutdown cear events and quit.
I really think you want your CLEAR EVENTS to be somewhere before your shutdown routine. See below. Is your READ EVENTS is in your main program before the DO FORM?
>The form has three command buttons
...snip
Do any of your buttons have the Cancel property set to .T.?
>What happens after you browse these dbf files is that when you
>close them them form returns. But if you print them without
>the noconsole qualifier the output of the last page remains on
>the screen. When you close it the program closes down.
The output you see isn't really a window you close. It sounds like you're actually closing the form (and, therefore, application)--IOW, the output is just displayed in the window, it has no existence as an object. It just totally messes up your form <g>. It makes sense to me that your app closes in this case.
>If you add the noconsole the the job is sent to the printer and the program
>which is an exe closes.
This sounds like a problem I had when I didn't have my READ EVENTS in the right spot (it was a long time ago, so I can't remember what I'd done). Also, do move your CLEAR EVENTS. It depends on your architecture. In 3.0 I had mine in my main form's unload. Now, in 5.0 I have it in my application object's release.
>The fix of setting focus to a command button on the form works
I don't think it's really a fix...and might be masking a problem that will just bite you in a different way.
Keep me posted, and good luck.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only