Yeah, I did, which I thought would have made VFP use that cursor as the default cursor if there was no alias prefixing the field name, yet I had problems with that.

>Hi Russell,
>
>did you set the Target Alias Expression for each detail band?
>
>
>>Hmmm...prefixing the fields with the alias gets the report printing from the EXE. Not a solution I'm fond of - such a bad habit to use an alias in a report, but sometimes necessary. I'll have to do some more testing to make sure it's behaving as expected in all cases, but I guess I'm good to go for now.
>>
>>>I am working with a report that needs multiple detail bands. I have a driving table and two child tables. I was running into a problem and in troubleshooting it, I decided to set up the environment via the command window and try to preview the report from there. I have the cursors set up as needed and the appropriate relationships set. But when I try to preview it, I get an error that says "< tablename > is not related to the current work area." Well, it sure is. The driving cursor is the one selected when I try to preview and the two child tables are related to it (I can see that in the Data Session window). The spelling is correct. I'm not using an alias in the controls on the report - I'm just using the field name. Any ideas why I'm getting this error message?
>>>
>>>Thanks,
>>>
>>>Russell Campbell