I would put the view in the dataenvironment. Adding the letter 'v' in front of all my views is helpful. I don't ever start a cursor with 'v'.
If you need to pass a parameterized view, simply create a private variable before calling the report. Set the relationship in the data environment.

Selecting another cursor from a existing cursor is done like the following:
select * from xyz where city = "GRAND RAPIDS" into cursor temp1

*-- create a cursor on the cursor
select * from temp1 where .t. into cursor temp2

If you need help in parametized views: email me at glmi-10@x2.alliance.net
I check email much more often than coming here.

Robert



>I don't think I understand. I already have the one to one above
>the details band and the one to many in the detail band. The
>report is based on a view which is named the same as the cursor.
>How do I query in a different cursor? Do I query the one to
>one relationship to cursor A and then select cursor A? Then,
>select * from A and the many child table into the cursor that
>the report is based on?
>
>
>>Susan,
>>
>>Put the one to one in a group above the details band. Don't query the one to many in the same cursor, put it into its separate cursor or in the data environment set the relationship (whatever works best). Put the one to many data in the detail band.
>>
>>Robert...
>>
>>>I have a report based on a view. The view is a one to one
>>>relationship between 2 tables and a one to many with the
>>>third. I have used this report in various spots in the
>>>application with success, but I have added a new tab to
>>>the pageframe. I append the new record to all three
>>>tables and issue a tableupdate when the user hits save.
>>>The records are saved correctly. Then, I issue:
>>> SELECT * FROM master, parts, sro;
>>> WHERE master.con_sro_no = m.print_pos AND;
>>> parts.con_sro_no = master.con_sro_no;
>>> AND sro.con_sro_no = parts.con_sro_no INTO CURSOR master_sro_view
>>>
>>> SELECT master_sro_view
>>> REPORT FORM pos NOCONSOLE TO PRINTER PROMPT
>>>
>>>master table = parent to sro table (one to one)
>>>sro table = parent to parts table (one to many)
>>>
>>>If I have more than one record in the many child table,
>>>it only prints one record. If I repeat the report command,
>>>the second command prints correctly. I put a browse in
>>>my code before I ran the first report and the first report
>>>command printed correctly. I have tried changing it to
>>>print "Report form pos for master.con_sro_no =
>>>parts.con_sro_no. When I have used this report
>>>before, none of the records where new ones, they were just
>>>being modified.
>>>
>>>Any ideas? Thanks in advance!
>>>
>>>Susan