Hi Craig,

Oooops! I guess I should have spent some more time studying that document!

I'll have to check to see whether my code works by switching the object from _SCREEN to _VFP. The MOVE method of the _SCREEN object seems to work differently also. I'll check into that too.

Thanks for the info. I thought I was going crazy (well, crazier).

Hugh

>It's not just your machine. There have been changes in this. The help file, under "Behavior Changes since the Previous Version" states:
>
>

>_SCREEN and _VFP coordinate properties (Top, Left, Height, Width) have been changed to better distinguish
>between the two windows they represent. The _VFP coordinates represent the entire Visual FoxPro
>application window (including menu and status bars). The _SCREEN coordinates represent the desktop area
>for example, the window to which ? output is directed).
>

>
>
>
>>Hi All,
>>
>>Has anyone else noticed the difference in the way VFP7 handles the _SCREEN properties LEFT & TOP and the method MOVE differently from VFP6?
>>
>>It seems that VFP7 _SCREEN.LEFT=0 places the VFP7 screen 3 pixels too far to the left (basically ignoring the left border) and _SCREEN.TOP=0 places the VFP7 screen 70 pixels too high (basically ignoring the top menu bar and standard tool bar - your machine may vary).
>>
>>Also, MAXIMIZING the VFP7 window seems to work as expected in terms of positioning its TOP and calculating its HEIGHT properties but still blows its LEFT and WIDTH (ignoring the window borders).
>>
>>VFP7's _SCREEN.MOVE method seems to work differently from VFP6 also. I'm still documenting the differences.
>>
>>Is this behaviour unique to my machine?
>>
>>Hugh