>>Dave & Antonio: I thought that the Report Form... command didn't take parameters in VFP3. Antonio, if you are passing parameters, then try using global variables instead. (Or, more OOP, use a form property on your calling form.)
>>
>>Barbara
>I still use VFP3. I have variables in my reports, which are called from .PRGs so there is no scope problem. Couldn't the procedure that calls the report just have something like varname = THISFORM.parameter or varname = THISFORM.parameterbox.value or wherever that parameter happens to be? Then the report would not be tied to the form.

This would probably work well with application-level properties, too. My concern, however was if Antonio was passing parameters in the REPORT FORM ... command. Also, the question of Private or Default DataSession may enter into it. Complicated :-(

Barbara