No George :) If I can get the pixels I could get the twips :)
>Mark I'm a human too :) and being honest just couldn't think sysmetric().
>Fred and Ed unfortunately I talked too early about sysmetric() being the answer. My sesssion was somehow a normal "maximizable" session. I should reproduce the effect first and I can only do it tomorrow. I'll be back if that doesn't work :)

I saw the other post < g >.

Not for you so much, but for any lurkers out there. Window's display elements, such as title bar height, screen width and height, are referred to as the "System Metrics". That's why the function name is SYSMETRIC(). It maps directly to an API call (naturally) named GetSystemMetrics().

>Here a short detail (Just can't remeber exact steps):
>-A VFP task open (max or norm ? don't remember)
>-Screen res. from 1280*1024 to 800*600
>-Anýother VFP task (fox screen max. or norm again can't remember :( )
>-Restore resol.
>-Return to first VFP task
>-Maximize
>-Maximized state is obviously about 800*600

Actually, I think what your seeing in VFP, you'd probably see in any other application. This action (mainimzing, maximizing) can be created in C++ (via the Application Wizard) without doing a line of code on our part.

A SWAG here is that VFP reads the HKEY_LOCAL_MACHINE\Config\0001\Display\Settings keys from the registry on startup and uses that information. These keys include both the resolution and desktop position for the Windows. AFAIK, there's no way to force VFP to re-read these. One of the SYS() functions does have it re-load registry items, but as I recall, they're only VFP specific, and not things like this.

BTW, if you get a chance to look at my OLE problem with Excel 2000, I'd appreciate it and any feedback you could give. There was a post about it yesterday in the OLE Automation Section. TIA