>>I am getting complaints from my users that use high resolution monitors that xfrx preview doesn't fill the screen. Any ideas on how to fix this?
>
>There is a XSOURCE thing on VFPX that expresses it solves the problem.
>
>I have not figured out what it'e doing nor is it working with me, but I think you should try it.
>
>See
>
>http://vfpx.codeplex.com/releases/view/10984.
>
>Please let me know your result.

I've been meaning to write a blog entry on this subject for a long time, but the short answer is... there are actually two issues regarding high DPI:

The first one affects the rendering of the report. If you are seeing overlapping lines on some reports, especially group footers, and the user has scaled up their DPI to 125% or greater, then check out the latest release on VFPX. It may solve your problem.

The second issue and the one being asked about here has to do with DPI scaling greater than 125%. On higher settings, Windows automatically scales up desktop applications, which is nice because your app might otherwise be tiny and unreadable on some screens. Unfortunately, this scaling cuts off parts of the report preview. This is internal to VFP and can't be fixed, short of writing a separate preview renderer (or hacking the runtime). The workaround is simply to turn off DPI scaling for your app (as recommended by Martina), leaving it running at the original resolution. This is probably ok for now, but as high-resolution monitors become more commonplace, users will start to complain that your app is too small. The preferred option is to do the scaling yourself, maybe break out those old scaling/anchoring libraries we used before VFP added anchoring. You could also leave DPI scaling on, export to PDF, and use a PDF reader rather than a VFP previewer.