>>>>>>>Is there a way to have a form take up the entire screen no matter which machine runs it? I've run an app on a machine with a 17" monitor and it looks totally different, only taking up only partial sctreen. Even some machine with the same screen as mine, the same happens.
>>>>>>
>>>>>>Form.WindowState=2
>>>>>
>>>>>I prefer to design all my forms using 640x480 limits (actually, slightly smaller than than to allow for menu and status bar) and then hard set the _screen.Width = 640 and _screen.Height = 415 prior to initializing my oApp. That way, I won't exceed someone's resolution and everything remains pretty much similar.
>>>>>
>>>>>I know it sounds like a kludge, but it works well and the users are comformatble with it.
>>>>
>>>>I also develop for 640x400 display. However, I prefer to have full _screen to allow smooth project enhancement by adding form resizing (maximizing) ability.
>>>
>>>I think _SCREEN.WindowState=0 (Normal) is best. Users should be able to do what they like. Also, the _SCREEN size should be remembered on shutdown and used when the program is started again. How would I make that happen? Something to do with FOXUSER and ON SHUTDOWN? How does it work for multiple users?
>>
>>Having normal installation (local exe, common dbc), you can provide local configuration table for each users to store individual settings, including e.g._SCREEN last layout. Anytime you start app, the first step is to open configuration table and apply the settings.
>
>What I describe is standard behavior for a windows app. Handcrafting a configuration the way you describe should work, but it shouldn't be necessary. VFP itself remembers what its own _SCREEN size and position was when you run it again. It seems like a VFP app should do the same thing in the same way, whatever that is.

This isn't magic...if VFP does that, it probably uses a method similiar to the one Edward described...you probably want to save one record per user...

Could Windows or VFP make an .EXE do this automatically? Sure...but this behaviour might not be desired in some apps...then what do you do?

At least this way, it is flexible...