Hi Lincoln,
You could put the SQL statement in the Init() of the Report's data Environment.

>>Great - it was very clear. Now FIRST let me introduce you to
>>< pre > and < /pre >
>>if you put these HTML codes before your text, it forces display as fixed pitch. Just remove the spaces around the codes.
>
>How's this?
>

>               SCARS: Left Cheek -- 2" crescent shaped scar.
>                      Right Wrist -- 1 1/2'" scar across wrist.
>                      Abdoman -- 3" apendectomy scar.
>
>               MARKS: Neck -- 2" circular birthmark on right side of neck.
>
>             TATTOOS: Left Forearm -- "Mother"
>                      Left Bicep -- "Rosie"
>

>
>>Second, the kind of problem you are having is the reason I use a single cursor for this information.
>>
>>Design a SQL-SELECT that will produce the fields:

>>
>>NAME          SSN           MARKTYPE    MARKDESC         MARKCODE
>>
>>

>>You would then order by NAME and by MARKCODE (this is so SCAR comes before MARKS). In your report, your Group1 would be name, Group2 would be MARKTYPE.
>>
>Okay, this is new territory for me. Everytime I think my learning curve is leveling off I run into the sidewall of the Grand Canyon. So much for the wizards. Just one question, where do I put the SQL-Select statements?
>I know it's pretty basic, but I generally don't use SQL-Select. (I don't even use views.) Do I use "Queries" and click "New"? If I use the Query Wizard or Modify program am I limited in the same way the View Wizard limits the number of joins?
>
>--lincoln