>
>If this is in a form, it often has to do with code running in a LostFocus or Deactivate event. This code wouldn't run in normal runtime, but when the debugger avtivates, it causes the code to run.

yes, I've seen that one and understood it, irritating though it is...
>
>I know it seems like a poltergeist, but the behavior is usually (always?) explainable. Who can explain it might be another question... :-)

as I've just said to Mark...

this wasn't so much a particular problem I'm having right now, so much as behaviour I encounter frequently both in the visual AND dos versions of Foxpro (where the timing excuse can't apply because it aint multithreaded)


Harry