>>>Today I continued work on a VFP9 report (reportbehavior 90) on a Win7 machine. Trying it later on my Win9 notebook revealed an odd result: Only a portion of the page is displayed, let's say 2/3.
>>>
>>
>>This under Windows 8? And like the maybe 1/3 of the entire right-hand side of the report is clipped in the preview? Regardless of the zoom preview? Yes, I've seen this on 2 different notebooks - one was a Lenovo the other is my MacBook Pro (resolution set to 1900 x 1200). I don't have any other Win 8 machines here to test with (and haven't had the time to set-up a VM). I've seen this clipping occur both with the VFP 9 previewer and with XFRX.
>>
>>I haven't had any time to dig into this yet, but I had tried different printer drivers with the same results.
>
>Yes, under Windows 8 (win9 was a mistake, of course). Good to read I'm not the only one. Indeed, 1/3 of the right-hand site is clipped in the preview and the printout.
>
>From discussions in Lenovo groups I know that Windows 8.1 gave improved resolution results as compared to Windows 8. That is, more applications gave nicer results. However, there still are several appllications that display horrible, e.g. Adobe Photoshop. So, it's the manufacturer of the application who can do something about it, but it's also a responsibility of Microsoft.
>
>Perhaps we are able to trace the responsible code in the reportpreview project and repair it. It is a VFPX project. I'll do some research this weekend if I find the time.

Okay, here are the resultls of my research.

Both this partial report display and the other issue I reported (Dragging causes a ghost rectange, Message#1592055) are related to the setting of the screen resolution. Rightclick on the desktop and choose 'Screen Resolution'. In my case it was set to 2048x1152. Moreover, I had chosen for enlargement of all items to 150 percent.
When I set these to 1600x900 and 125 percent (normal), the issues are gone.

I think there is some related code in (see Reportpreview project) frxpreviewform.init(). The following piece of code gave 96 (screen dpi) as the result. Now the result is 120. Probably that code needs a revision for the repair of the report issue. The other issue is typically vfp. A repair via any vfpx project is unlikely.

#define LOGPIXELSX 88

declare integer GetDeviceCaps in WIN32API integer HDC, integer item
declare integer GetDC         in WIN32API integer hWnd
*declare integer DeleteDC      in WIN32API integer HDC
declare integer ReleaseDC     in WIN32API integer hWnd, integer HDC

local hdc, screenDPI
hdc    = GetDC(0)
THIS.screenDPI = GetDeviceCaps( m.hdc, LOGPIXELSX )
ReleaseDC( 0, m.hdc )