Carlie-

Thanks for the information. I haven't had any problem with using private datasessions and printing from the preview toolbar, but then I was using the report DE.

Have you told us what version of VFP? 5.0a? Build 415? Can you print to printer programmatically? I ask because I don't know what you mean by "it's fine from the form itself." Do you mean it *prints* from the form (i.e. printing programmatically works)?

I know that you are not using the cursor name prefixed to the field < s >. I was asking about prefixing the table name to the field in the report as a test...I'd still be interested to know what happens if you do, just for the first field. I don't think that's the *actual* problem because lots of people would be here screaming if that was a bug < s >. But it would tell us pretty fast if the assumption that the correct cursor is selected is correct.

Last question: is the report datasession private (sorry, it's been a while on this thread and I don't remember if you told us).

>No, I'm not using a table name/alias in the report itself.
>I select the correct table before calling the report. The report is
>fine from the form itself but does not print from the
>print preview toolbar - that's where the "variable not found"
>error appears. I think there is a problem with using the
>print preview toolbar from a private datasession.