>>>Any idea as to why I'm getting an Open dialog box when I try to print the report? There data enviroment for the report is empty.
>>
>>what are those text boxes tied too? any chance the report is just confused and thinks they are tied to fields? Check the frx maybe, and/or try putting a m. in front of the source specified for those textboxes if your trying to use variables. HTH.
>
>
>The text box in question is referencing a property of my application object: oCUWS.apperror
>
>I can see how this looks alot like 'mytable.myfield' and how that could make things confusing. Any suggestions.

You might try EVAL('oCUWS.apperror'), or pulling the properties to PRIVATE variables before the report runs and referencing the variables in the report.

Also, the VFP report writer is built around operations on a table/cursor/view; perhaps creating a temporary cursor, pulling the values for the report to its fields, and reporting against that would work better.

Alternatively, you might use one of the other output mechanisms like the @...SAY, ?/??/??? or text merge facilities to create your output.