>Hi Cetin,
>
>I'm suspicious of the trim with ellipsis function. What happens if you just use a traditional trim function?
>
>Some other questions to help you debug your situation:
>
>1. What's your default printer set to?
>
>2. What is your default printer's quality setting? (As an aid in debugging: Try setting it to Draft to see if this fixes your problem)
>
>3. Does your report include any images?
>
>4. Does your output fit within the printable margins of your report/printer or does VFP have to clip your output along the right margin?
>
>Regards,
>Malcolm

Thanks for the replies guys.
Here is some more explanations and solution I ended up with.

The SQL query returns 28 columns, 1 memo (generally empty or few lines), rest are integer,date,char fields. No image, general. 8556 records, each record fits to a single page so 8556 pages report (and this was a test, real ones might be more - not printing at all just preview).
When I set reportbehavior to 90 and do this:

report form myReport.frx preview

It took around 90 seconds for it to complete and in fact it could never complete. Each trial ended with a crash ("Send error report..." thing). I couldn't see any page, at background there was a message saying "Not enough memory to complete this operation" -not responsive- followed by a "Resource manager internal consistency error". Then VFP closed down. OS resources seemingly mucked up, many areas on screen had painting problems. I rebooted, erased foxuser and retryed for a few times to no avail. All ended in same scenario.

Then I ran the same report using MindsEyeReportEngine.ocx. Voila. It was faster and it showed my report. No crash. I tried again and again and it always showed up with success. I watched the memory using both and ME used less memory also.

Probably VFP has a limit for pages somewhere I don't know. Anyway I have ME license and I'm happy Rich had an update using ReportListeners:)
PS: I didn't try Nodialog. It might be faster but I suspect if it would work.
Cetin