Andrus,

>>
>>One workaround is to use a private datasession for the report, which would preclude using the FOR clause. Personally, I prefer to create a cursor with SQL select statements before running the report. The NOWAIT clause may still cause problems even in that scenario.
>
>I havent seen ANY datasession disappearing or ANY problems except REPORT NOWAIT bugs. I run REPORT PREVIEW NOWAIT
>from a form with private data session.

Running a report with its own private datasession is not exactly the same thing as running a report from a form with a private datasession. The Kilofox book refers to the report losing its datasession when the NOWAIT clause is used. I'm not exactly sure what that means, but I still think it is part of the problem.

I do know this...you can create a report with a private datasession, and create a cursor containing what you need in BEFOREOPENTABLES. Then when you run the report with PREVIEW and NOWAIT, you can print from the preview button, and it does not crash. This is why I suspect it may be related to the datasession.

> I modified genrrepox to add automatically
>the following code to form datasession. This respores datasessoin and allows
>use of navigation keys for preview: this fixes another bug in VFP: it does'nt allow to
>use arrows to move in report preview.
>

Not being able to use the keys in report preview is annoying. What is genrrepox? Thanks for posting the code...