I figured it out........... there is a THISFORM.REFRESH with code that sets the values of those two Properties during Refresh........ hence, under a controlled environment of tracing, I was not refreshing at ALL (of thisform) until the end of the code.... but during exectution, the form was exposed and refreshing when necessary, and resetting those properties to uncontrolled values (at least, what I was not wanting them to be).

So, to fix things, I left the REFRESH alone (who knows what danger lurks there?), and modified the main code of the procedure, to reset those properties to saved values, BEFORE executing the called methods.

Works fine now..... sigh.......... on to other bugs!!!

>I've had this happen years ago, in some other code, but my memory fails me on how to fix this quickly.
>
>I am debugging code in the debugger in VFP 8.0 SP1. Works fine there... beautifully!
>
>But............... when I create the EXE and run it outside of the the developement platform........... wham!!! It does not run at ALL like in the debugger.
>
>The code calls many methods of THISFORM during execution. There are two properties that I am tracking during execution.... and these two properties maintain their values as they SHOULD, during debugging. I have added some WAIT windows to display the info of these properties when running outside the development environment, and they show the values CHANGING about halfway down the code......... weird!!!
>
>OK, what am I overlooking?
>
>Thanks!!!