>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.
>
>

Jeff (and Bruce, since you suggested a similar strategy)-

I think this strategy is severely politically incorrect. If a user has his screen resolution set to 640x480, it is because that user wants to see everything large. He can go around his entire operating system and look at every application, and nearly all will have similar or identiacally sized textboxes, fonts, buttons, etc. Then he goes to your app, which just resized all of its elements to cram all the controls you deemed necessary to fit in the user's tiny screen. Now your app is the only app on the machine with small buttons and text. And the only app in which the far-sighted use has to squint to read the UI. The same goes for users with unusually high resolutions- I set my resolution high because I like to fit a lot of stuff on the screen. But your app just blew itself up to cover my valuable screen real-estate, negating all the benefits of my huge monitor.

Is this really what you want to do to your users? Didn't they make the size decision when they set their resolution in the first place?