>>>>From VFP9 Help:
>>>>

>>>>Maximum # of pages in a report at run time: 65534
>>>>In object-assisted preview, limited by available GDI+ resources
>>>>

>>>>On my system, REPORTBEHAVIOR 90 object-assisted preview seems to crap out consistently at (exactly, or very close to) 5,000 pages with an error message about GDI resources exhaustion.
>>>>
>>>>Has anyone else hit this limit, and at what #pages?
>>>
>>>Not related to your problem, but I found that even if I use report form myReport range 1,2 it still seems to try to run the report for the whole file... And it doesn't immediatelly react on pressing Cancel button in the Printing dialog.
>>
>>On digging a little deeper, I found a seemingly-related topic on the Wiki in the VFP9 SP1 bug fix list ( http://fox.wikis.com/wc.dll?Wiki~VFP9SP1BugFixList~VFP ):
>>

>>REPORT PREVIEW GDI handles limitation with many pages
>>

>>I tried incorporating it into a method with a call like
>>

>>REPORT FORM ( lcReport ) OBJECT loListener GDI
>>

>>but VFP9 SP1 complains about "unrecognized keyword in command". Maybe this extension is REPORTBEHAVIOR 80-specific but even so I don't think a REPORT PREVIEW GDI command would compile. I think we need more documentation on what has changed (if anything) and how to use this.
>
>The SP1 generates the error you got. VFP9RTM blows up.

Thanks for the clarification. So, the entry in the SP1 BugFixList is very ambiguous, I can read it in at least 3 different ways:

1. (REPORT PREVIEW GDI) (handles limitation with many pages)
- i.e. they introduced a new keyword ("GDI") that "handles" (fixes) the problem so it no longer occurs

2. (REPORT PREVIEW) (GDI handles limitation with many pages)
- i.e. improved use of GDI (or use of GDI instead of GDI+) "handles" (fixes) the problem so it no longer occurs

3. (REPORT PREVIEW) (GDI handles) (limitation with many pages)
- i.e. acknowledging there is a problem with GDI handles when a report has many pages. It doesn't say that the problem is fixed, it doesn't say that this problem no longer crashes VFP, it doesn't say anything about a new error message being generated.

WAFWOT (as we used to say in my fish guide days)