>>
>>Well, O.K. I know you've got to work trough ODBC or FOX 2.6 tables, but for the rest i find it's quite straightahead.
>>
>>I must admit that it cost me a lot of time to intergrate it with my framework. But from now on its almost as easy as using native VFP reports. The only drawback I'm experiencing is that I must convert each table to be reported into a FPW 2.x format and use *.IDX indexes. But once you know this, it's quite comfortable to work with CR.
>
>Why do you do it this way? Can't you run a PRG that has SQL SELECTs and creates one cursor in the correct order, then COPY TO File TYPE FOX2X?

Craig,

One complex report required a one to many relation within the report. I could not comfortably manage it by putting all the info into one table. I had to do summary calculations on the parent table. If I joined the parent and the child table into one I could not handle the parent table calculations because of the duplicate rows.

Walter,