>George
>
>>There are two possibilities that come to mind. The first, but highly unlikely >in my mind, is that the executable being call minimizes the form. The second, >would be that the logical variable being assigned has an assign method that >would fire when its value changes. If it did, perhaps the code within that >method is setting the WindowState to minimized (1). These are the only two >possibilities that come to mind. I've never seen this sort of behavior in VFP >or any of its predecessors.
>
>I know - it puzzled me also.
>The variable doesn't have an assign (or access) method.
>The chap who wrote the exe says it doesn't minimise the form - and it works fine for him.
>When I change the VFP forms ShowWindow property from 2 (Top level form) to either 0 or 1 - then the form doesn't minimise !
>
>Regards
Anna,

About the only thing that I can suggest is that you create a WindowState_Assign method. This won't fire unless the form's WindowState is programmatically modified. IOW, any change by clicking the minimize, maximize, or restore options won't do it. If it does fire, and you've set a breakpoint, you can see what's doing it via the Call Stack.

FWIW, I've tried to replicate the problem without success.