This is more or less a repost of message#01686902, only we know now it's on two special frx files.

Hi Marshal,
Sounds odd.
My first ideas
Run a decent RAM test on your machine, check hardware. (reconnect anything you have access too, remove the dust)
Enough free space (>25% ) in each drive?
Any chance to set up VFP in a virtual machine on a different comp and test there?

NTDLL.DLL is a kernel modul, whatever caused it to fail is on a different level. You could run a (external) virus scan over your machine, but I guess it's not the problem.

Most stupid question: Can you change to a different page in preview and back?
Try to run with limited range (2 or 3 pages)

REPORTBEHAVIOR 90 renders all pages, and just displays them on a canvas on a form out of internal storage. So the problem must raise after the main work is done. Something is unable to repaint the page to the canvas for some reasons, get odds out of some memory or is corrupted for a different reason. This is GDI+, so I think the problem is not VFP sided.

Now the VFP steps to try I see:

- compiled version means running the exe out of the IDE or out of Windows Explorer?

- Check that you use the right listener app (_REPORTOUTPUT)
- Check that you use the right preview app (_REPORTPREVIEW)
-- any chance that your EXE is changing this on startup? Something compiled into the exe, path or the like? Different versions(files) on the comp?
-- The standard value is stored in Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualFoxPro\9.0\Options, not in FOXUSER.dbf
- Try to get the apps from somewhere else (customers comp, second comp ...)

- Any other changes to the report apps? Private listeners, XFRX or the like?
- Are you running like REPORT FORM .. OBJECT .. ?

- you are sure the version in the EXE is the same as on IDE? (Path problems,excluded, whatever)

- try older version(s) of the frx files
- try to pack / validate the frx file

- If all fails, the code is on HOME(1)+"Tools/xsource", use the app from there and try to SET STEP ON into the handler. The code is not very tricky to debug.
For all I remember, it is like "MODI CLASS frxpreviewform OF frxpreview.vcx METHOD SetZoomLevel"
Pls report the code where it fails.

Lutz
>I've created a new post that is a bit more detailed. Please answer here Lutz.
>
>>Duplicate to Thread#01686893. Should we answer here or there?
>>
>>>Whenever I attempt to change the Zoom setting when Previewing 2 particular Reports with SET REPORTBEHAVIOR 90, see a brief flash of the re-scaled Preview followed by the Development Environment crashing. Other Reports work correctly and this does not occur in the compiled versions running the same 2 reports.
>>>
>>>I looked at the Windows Error Log and it appears to be an issue with the NTDLL.DLL file in the Windows/System32 folder. Stumped as to why this is happening for these 2 reports.