>>No, actually I was trying to using the detail band to try to get data for the summary band. I don't think adding another field will work. In creating the cursor, I'm in a situation where I need the detail info (so using group by won't work for me), but I also need summary info. This is probably a job for two cursors, but I'm trying to design a generic reporting class which uses one cursor.
>
>Thanks everyone for your help. Interesting turn this thread has taken.
>
>I've stuck with the native report writer and the UDF's. I put text fields on the report that call functions which return a formatted string. Works great except it's a little slow in the print preview and frighteningly slow when someone tries to preview the last page.
>
>I just don't understand the report writer though. It hasn't changed much since 2.6 Win while the rest of the app has improved greatly. The print preview window is a pain in the butt. The print preview toolbar is difficult to handle (and when you do handle it, it's with code that could only be described as "cheating"). When you print the report, a dialog comes up with the name of the FRX and the foxhead icon.
>
>Minor problems mostly but they make it difficult to take VFP seriously for a professional app.
>
>I don't suppose anyone has come up with a "better way" withing VFP (not using a third party tool)?
>
>paul

I'm willing to stand for Fox Report Writer :). It may fulfill any reasonable kind of report. It's just question of time you are willing to invest to development.