>>>The problem is internal to VFP and can't be fixed directly without hacking the VFP exe/runtime. If Microsoft offered true support after VFP9 SP2, this would have been fixed a long time ago. You have to take another route to workaround it. Another option I forgot to mention... you could run the report/preview in a separate EXE. You could leave DPI scaling on for the main app, and turn it off for the report EXE.
>>
>>The big problem is:
>>
http://www.blitzbasic.com/Community/posts.php?topic=99385>>
>>Strange I made it and then I found out that BlitzMax calculate same thing corect. DesktopWidth() returning corect value on 125% but fails on 150%
>>I found out that problem is not in the BlitzMax ,Win Method GetDeviceCaps(hdc, LOGPIXELSX) returning wrong value.
>>100% dpi=96
>>125% dpi=120
>>150% dpi=96 :)
>>
>>MartinaJ
>
>I'm going off of bad memory here, but when DPI scaling is on, I think 96 DPI is correct. Windows is scaling up the app, so you want it to think that it is running at a standard 96 DPI. Turn off DPI scaling, and you'll probably get a higher number for 150%. VFP must be getting mixed up between the two internally. I was hoping XFRX would come up with some magic to fix this. :)
https://eqeuscom.atlassian.net/wiki/download/attachments/5734404/xfrxlib_157_2015-10-02.zip?version=1&modificationDate=1443810568763&api=v2MartinaJ
