Not really "explain" but I have run into weird stuff on forms and events when .Init() had not fully run.
As Wait Window besides sys1104 also clears some events, I stay away from it init-phase, similar to timers and any bind-event stuff.
Debugger open eliminating the problem also points in a backward way to events somehow disturbed
;-)

The other really weird stuff happened back in vfp6 in a with .. endwith, where the datatype of eturn value sometimes was changed. Never got a good explanation, just removed with.. from my coding, using an explicit local var to save a deeply containered sub- or COM object needing to be worked on in several lines.

rather unsystematic Qs:
Property where defined in object hierarchy (vcx/prg) or runtime with .addpropertied() ?
Sitll initial value or already changed a couple of times ?
every object running in same DS ? Had once a service factory in default DS and added finished service objects with private DS.


>A property of a form was unexpectedly getting cleared (that, is set to the empty string), but only under certain circumstances and only with the Debugger closed. When I traced the code or even just had the debugger open so some DEBUGOUTs could work, the problem didn't occur.
>
>That meant I had to track it down via logging to a text file. I kept adding logging until I found the culprit. The line of code causing this property to clear was:
>
>

>wait window timeout 1 'Record saved.'
>

>
>At the end, I had logging immediately before and immediately after that line and that was when the property changed. Comment that line out and the problem goes away. As I write this, it occurs to me to try it without the timeout clause (maybe add a WAIT CLEAR later on).
>
>Anyone have any thoughts about why a WAIT WINDOW would have any affect on the value of a form property?
>
>Tamar