>Thanks for the tip. All my reports run off of SQL statements (SQL passthrough). How is the best way to make that cursor available in the DE of the report?
>
>>
>>Maybe I should be a little more explicit
>>
>>DEFINE WINDOW TestWindow FROM 2,2 TO 30,30 IN SCREEN NAME objectname TITLE "Modeless Report Preview" DOUBLE GROW FLOAT
>>
>>REPORT FORM TestReport PREVIEW IN WINDOW TestWindow NOWAIT
>>
>>Insure the cursor/table being reported on exists inside the report's data environment.
>>Using the above method I attain a modeless report preview without the problems you've mentioned.

One other thing : ACTIVATE WINDOW TestWindow
is required....

perform the sql passthrough inside the command window...

read the cursor into a temporary table....
SAY --> c:\temp\TestTable.dbf

THEN build the report with this TestTable.dbf in the data environment.

you can adjust the location of the TestTable.dbf in the
BeforeOpenTables event by adjust the DataEnvironment.Cursor1.CursorSource property.... this allows your application to control the location of this temporary table.

this way the dataenvironment will look for the cursor/table in the correct location.

I recommend deleting this temporary table once processing is complete.

good luck