What could throw a spanner in the works is if the user changes the size or position of the taskbar.
On a similar note, the DPI setting could affect what you'll need to do as well (e.g. if user has selected "Large font" or "extra-large" font size, then your screens will need to be larger in pixels to make the screen content fit).

>Yes, this is what I did; changed the screen size at run-time. The logic is: check the screen resolution and if it is less than 960 (height), change the size of the window from 680 to 520. I tested it on my PC and it works.
>I am sure if there is a problem, the customer will let me know.
>
>>Did you plan for runtime changes to screen size ? Happens in my surroundings (VirtualBox hosting the "system") sometimes even by mis-clicking. Even on more traditional HW leaning settings it could happen: switching monitor, going from lap screen to office etc.., Might be better to look for WinAPI + Eventbinding than adding a new timer or a check branch to existing timer...
>>
>>my 0.00022€
>>thomas
>>
>>>>Hi,
>>>>
>>>>I have a window/form which is only works on a larger monitors. So, in order to show this window/form on a small monitor, I need to reduce it (at run-time). Is there a way to find out the current screen/monitor resolution so that I can make the height of the window smaller?
>>>>
>>>>TIA
>>>
>>>The sysmetric(2) that Dragan suggested shows exactly the height of the monitor I have now. Which is what I am looking for.
>>>
>>>Now I am trying to figure out the cut-off point of the resolution (on a customer's PC) to make the window/form smaller. The window/form I have is 680 pixels (at design and run time without making any change).
>>>What do you suggest I should look for (in sysmetric(2)) to start reducing the height of the window/form?
>>>
>>>UPDATE. I found how to make this work. I can change the resolution on my PC and then see if the form completely appears. It looks like 960 is the cut-off point. That is, if the screen is smaller than 960, I need to reduce the height of the form.