>Thanks for input. I have taken your advice. I check the resolution at startup. If the resolution is less than 1024 I run a modal form that allows them to call the display applet. It works very well. However, as I suspected they soon tired of that and now want to do everything automatically.
>
>The company knows that the app must run in 1024 res. Some of the users prefer 800. The users must use the app to conduct business so the philosophical questions all become moot. I have suggested that they buy 17" or 19" monitors but that is probably in the distant future.
>

If there is a real requirement that the system be in 1024x768, what's the headache - test and rat them out for failing to adhere to the company policy. I stand by my recommendation that the user choose how to implement the requirement - Active Accessibility viewporting, and the presense of at least three display mode related factors controlled via the API - color depth, refresh rate and font/icon size, and whether or not the registry should be updated, and exactly when you need to check to ensure enforcement of your application's video directives, will be factors here.

You've not addressed the issue of hardware that may be inherently non-compliant, either unable to support the video mode at acceptable depth, or in the case of digital flat panels, support the mode at all without viewporting, may arise. 1024x768 at low refresh rates tends to exhibit flicker. Interlaced displays may be a nightmare.

At least make your concerns known, in writing, approved by management that signs the check for your delivered product. I'd investigate buying a solution rather than rolling your oiwn if at all possible if you are not familiar with the details of Windows APIs and messaging.

>As I mentioned earlier, I don't have any experice making API calls. Is there a code snippet I could use to automatically change the resolution?
>
>Thanks
>
>Glen Mettler