>It shouldn't matter if your application supports different screen resolutions. My base form and toolbar classes have methods which accomplish this.
>
>As the application object loads, a simple API call determines what resolution the user is using and makes that information available to the set resolution methods of forms and toolbars which, in turn, makes the necessary resolution adjustments to all contained objects during instantiation.
>
>I think there are examples of this in the UT file section and maybe something in the FFC. There was an excellent example of this in FoxPro Advisor about a year ago.
>
>
>>What's the standard for screen resolution for forms that are to be included in over-the-counter software to be sold in stores and used in homes and businesses.
>>
>>I always thought/assumed it was 640x480. Or is it 800x600 now? I know it also depends on the application, but as a rule or on average what is considered the best screen resolution to use when developing a form in VFP that might some day be sold to the general public?
>>
>>What do you think? Thanks for your input.

My strategy is to let the user make the decision on how large he wants the application. I design the application for 800x600 (my company finally upgraded from a 640x480 default resolution, hurray!). If the resolution is set higher, I don't automatically resize. The user can resize by dragging the VFP main window to the size they prefer. When they do all forms resize in proportion to the size of the main window when they are opened. When they exit the application, I save the mainm window size they chose in the registry. The next time they load it, they get the size they prefer.

This way the user that likes to have a lot of small windows on his high resolution monitor is happy and so is the user that wants a bigger window that's easier to see.