>_SCREEN.WindowState = 2

Yeah, that does work. Also setting the window state to maximized in the shortcut works, too. But it's not exactly what I'm after. I'm developing in 3.0 and a lot of our users have win311. You can't start a program maximized with Program Manager. I would like to be able to have the main VFP windows coordinates and windows state pre-determined before you even see it. It works that way when you run VFP. It keeps it's window state and coordinates in the Foxpro.ini file. I wish this feature would work with run-time applications as well. I wonder why they (run-time applications) ignore the foxpro.ini?

I usually like to set the main VFP window to 640x480 to accomodate all resolutions. (I then "fit" my screens into it with no title/border in an effort to "conceal" the main VFP window.) On machines with higher resolutions, I want the VFP window centered. On 640x480 machines I want it to be maximized. In both cases I want the windows to be exactly where it's supposed to be without the screen bouncing around (starting out normal, then maximizing or centering). This is certainly not an issue with 5.0 and top-level forms. I may just have to live with _screen.windowstate=2 in my main prg. :(

Why can't everyone be on 32-bit windows!? :( 6.0 is comming soon and I'm still having to code in 3.0!

At any rate, thanks for you help, Paul!