That did the job perfectly. I was testing something similar last night with common fields in the cursor but I like your idea better because it appears easier to handle and debug. Thanx muchly :-)

>Well I thought you had a relationship between the two tables since you said Student Number was common to both, and that perhaps you could do a regular SQL join on that field. But if that's not the case, a UNION would work and I am forced to use that approach in many of my reports. The idea here is to create a temporary cursor that is structured in such a way as to drive the report. For example, maybe a table structure on the cursor like this:
>
>StudentNum
>CourseID (only Containing data for records from Course Table)
>CourseInfo (only Containing data for records from Course Table)
>EvalID (only Containing data for records from Evaluations Table)
>EvalGrade (only Containing data for records from Evaluations Table)
>
>Then when you setup your report, in the detail band you will want to have CourseID and CourseInfo with a PRINT WHEN Condition of NOT EMPTY(CourseID). And over top of those two fields, put EvalID and EvalGrade with PRINT WHEN condition of NOT EMPTY(EvalID). As you can see the the cursor wont be pretty relational data, and the detail band in report wont be pretty either, but it will make the report work. HTH