From the VFP9 Help File:

The Report Engine evaluates any expressions you
have used as target aliases in your report layout,
before it begins processing your report. If these
expressions do not evaluate to aliases currently
in use, the error "<alias> not found" occurs. If
an alias is in use, it must either be the same as
the driving alias or related to the report's
driving alias. Otherwise, the error "<alias> is
not related to the current work area" occurs.

I have created a report with multiple detail bands and each band is based on a separate cursor created by a SQL command and sorted the way I want it. Now this little caveat above says I need to SET RELATION to the driving cursor.

I have created an index on the (updated correction:) parent cursor, and issued "SET RELATION TO Log_ID INTO ParentCursor" for all 3 child cursors. The Target Alias for the first detail band is set to the name of the parent cursor. The Target Alias for the 2nd, 3rd, and 4th detail bands are set to the appropriate aliases of the child cursors.

I still get the "alias not related to the current work area" error message. I have made sure my parent table is the current workarea when I try to run the report. If I remove all the Target Aliases, the report runs but I only get 1 record in each band. What am I missing?

TIA!