This concept would work just fine. I don't have an example, but you could approach this a number of ways. One way would be to build the cursor ahead of time with records for the "real" data and however many records required for the "lines". You could add a field to the cursor that distinguishes the real data from the lines and then use "Print When" logic to figure out which items to print.

Another concept that might work is to add the records on-the-fly. By this I mean that you could call a UDF or method from within the report that goes off and adds some additional records to the actual cursor you are printing from. This idea gets pretty sticky, but it's doable!

Cathy

>Cathy/Andy,
>
>It seems like this would be a lot of effort just to put lines on a report, but he could put some more records in the report cursor, put the line in the detail band, and use "Print When" to determine if this is a "Line" record or a true detail record.
>
>Cathy, do you have a thread you can point him to that gives more details on that concept?
>
>>You can't programmatically repeat the shapes drawn on the report. Your only option to use those would be to add a bunch of them and change the print when logic of each one to suppress it if it isn't needed. The drawback would be that the band would have to be defined very tall and when VFP checks to see if there is enough room left on the page, it doesn't take into account any of the print when logic. It only looks at ALL the possible objects and checks for that much room.
>>
>>
>>>That is real close to what I need but I want to do that to lines I draw on the report rather than use '_' or '-' or '=' or '[ ]'
>>>Any way to make drawn objects do that?
>>>
>>>