Got it!!!

There was a CLEAR EVENTS in the QUERYUNLOAD event..... so I wrapped it with a

IF VARTYPE(m.mid) = 'U'
   CLEAR EVENTS
ENDIF

the m.mid is defined in the calling big daddy program.....

so this will keep the CLEAR EVENTS from being called when run when running under the big program (cause m.mid is defined there).


WHEWWWWWWWWWWWWWWW!!!! That was a tough bugger!!!

Merry Christmas and Thanks to you and ALL THE OTHER GURUS HERE!!!!!

Much appreciated!!

Tommy

>>No "CLEAR EVENTS" there.
>>
>>I call the form using a PRG with following code...
>>
>>

>>_SCREEN.Visible=.T.
>>SET SAFETY OFF
>>DO FORM select
>>READ EVENTS
>>RETURN
>>
>>

>>
>>>Do you've by any chance "CLEAR EVENTS" in the Destroy of your form?
>>>
>>>>Hi Again, Gurus!!
>>>>
>>>>I have a SLIGHT problem here. I wrote a utility in VFP 7.0 SP1 as a standalone app.
>>>>
>>>>Worked great!!
>>>>
>>>>THEN...................................................
>>>>
>>>>I found out it was to be called from another app.... the big bad app here where I work at.
>>>>
>>>>Well............... after fixing up a few bugs, I still have ONE bug to fix...
>>>>
>>>>
>>>>When I select the OK button on MY form to kill the form, it calls CLICK:THISFORM.Release... and it disappears... NATCH.......... BUT!!!
>>>>
>>>>IT TAKES OUT THE CALLING PROGRAM TOO!!! I've banged my head here for about 30 minutes.... have you run into this behavior???
>>>>
>>>>Thanks!
>>>>
>>>>Tommy
>
>Tommy, If your program runs as a stand alone app, when you release the form, does it exit? If so you would have to have a clear events somewhere in order for it to get past the read events line in your program, otherwise your program would hang with the VFP Screen visible after your form is released waiting for events. Do you have an "On shutdown" procedure that does cleanup on exiting the form which may be executing clear events and quit? As someone said and as documented in HELP: Note that only one READ EVENTS can be active at a time. If a READ EVENTS is in effect, any subsequent READ EVENTS commands have no effect.
>
>A clear events anyplace in your app or the calling program will terminate the event processing begun by the first read events unless your app is called by RUN/N or !/n which case it would be running in a separate session independently.
>
>You should search all files in your project for clear events and quit and make it conditional only when program(0) = your program.
>
>HTH