Yau,

Private variables suffer the same problem as locals when using the NOWAIT clause...they go out of scope. Public variables are certainly not the way to go (each report that is open will see the same public variables).

I have tried putting this information into custom properties of a form, but when using NOWAIT clause the same problem happens as private and local.

Are you allowing the user to view multiple copies of the same report, but with different parameters (or data)? Since you are using a private dataenvironment for the report, how does the report know exactly what data to print?

If you are trying to show more than same copy of the same report, I think you have to give the report a different name (make a copy of the report format files) for each time you display it.

I would recommend that you store this information in a temporary table, and add that table to the data environment of the report. In opentables() of the dataenvironment, you can locate the correct record in the temp table, and refer to it by its full name from with the report body itself (for example, reportTemp.parameter1).


>Steve,
>Yes, I use the nowait and point the report to a window to allow users to have multiple reports concurrently.
>Any suggestions on how I can resolve this?
>Yau