>>SeaGate's job is to get me and my customers to like their product. The Report writer is simple enough for me and my users right now. If anything, we could add 3 enhancments to it, and it woudl hold over most Report Writer problems for quite a while:
>>
>>1. Create DYnamic properties like in grids.
>>2. Add support for multiple detail bands
>>3. Better support for graphics
>
>4. Duplicate anything that's in the Format menu bar into the Properties dialogue
>5. Allow subreports; subreports in separate files would be even better than CR's embedded subreports which can't be resync'ed wiht their free counterparts (still using CR 6, maybe this was fixed until 8).
>
>If it will have to be CR for Fox, would they please steal the layout windows from VFP's report designer? I'm fed up listening to my colleague cursing CR for third day in a row... his ultimate statement was "CR was written by someone who hates his users".

There were major UI changes in CR8. I think the subreports problem was fixed too.


>
>>Using CR is great, go for it, but I don't understand the tight integration, thats all my point here is.
>
>Tight integration would be using the already open cursors, indexes and relations. One thing which annoys me with CR is that it needs the tables to be there - can't tell it to run on whatever you give it, unless you Copy ... Fox2x, and then say oCR.datafiles(0)=lcMyTemp2xCopyOfCursor, which works fine as long as you use only one table and don't try to use any indexes or relations on them (talking CR6 again, but if it wasn't fixed as late as v6, get a clue).

That would be difficult to do. CR would need access to VFP's memory space.