>You see, the two cursors (one for Detail 1 and another for Detail 2) are related (with SET RELATION command). Therefore, VFP "points" to both cursors at any time. Therefore, checking for a presense of a field in one cursor or another does not seem to work. I was thinking that if there was a function indicating that the report is printing a record from Detail 1 cursor or Detail 2 cursor, then that would be a good SomeCondition.

OK, I see.

The detail band has an "On entry" expression, perhaps here you can invoke a function that increments a variable for every record. I guess this would be separate for each of the two detail bands.

Similarly, a report field has a "Print When..." condition, where, of course, you might invoke any function.

Provided the "Calculations" by itself (in the individual field, in a detail band) isn't enough.

Otherwise, it is starting to get a little awkward.

On the other hand, one thing I have been doing for a long time is prepare all the data (cursors) beforehand, especially data that is complicated to get through the report. For instance, you might loop through a R/W cursor, and increment a separate summary field.