I've seen this behavior when several activex objects are part of the environment. The reference to an OCX method does not neem to byte :) when referenced procedurally.

It's as if the debugger slows "it" down enough for the references to catch hold.

WHat I had to do in those cases was "borrow" an unused method in an OCX control to fire the events.

One thing you could try is to move the methods to a procedure (in cases where they are added methods on a form) and pass the "thisform" to be used as a reference. Or, conversly, place external procedures in a custom form method.

I hate it when that happens!:). It's a weird one - I have tried in my cases to isolate it - but always went back to borrowing "available" methods in other OCX controls to fire the events.

Are you usin binding or table buffering. Try to assign the values with an "=" sign rather than the bind,

>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!!!