>>>>2. Add support for multiple detail bands
>>>
>>>You can do that now.
>>
>>He said support for. You can do this now, but it _ain't_ pretty.
>
>I have no problem doing multiple detail bands. Maybe I setup my data differently than you do and that's the difference.
>

Could you expand here? I know the common techniques to get multiple detail bands, and unless you have much more tolerance than I do for Rube Goldberg code, you must have some cool trick up your sleeve.

>>To add to Mike's list, I would like to see:
>>
>>Full report object model.
>
>What would you like to see changed here?

oReport = CREATEOBJECT("MyReport")
oReport.Bands("Header").AddObject("field1","field")
WITH oReport.Bands("Header").Field1
.top = 1
.left = 5
.Expression = "MyTable.MyField"
.FontColor = RGB(255,0,0)
.FontBold = .T.
ENDWITH

#DEFINE TOPREVIEW 16
#DEFINE NOCONSOLE 32

oReport.Run(TOPREVIEW + NOCONSOLE)

>>Reporting Events. (OnFinishGroup, OnStartFooter etc)
>
>Hmm... I thought I saw something about this in CR 8.5. I'll have to check.

I don't care if it's in CR. Even if it was, it would allow me to call my own objects.

>>IDE overhaul. (Property sheet for controls/labels, etc)
>
>This is getting better, but could still have some improvement. There are property sheets for objects. Here again, what do you want to see changed?

A modal dialog does not a property sheet make. Try making adjustments on more than one control at once. The current way is a huge pain in the ass.

I can't believe you're attempting to defend the status quo with the current report writer. If the rest of the product was built like this, not a one of us would be VFP programmers.