>I can answer those questions from 2 different perspectives...
>
>From the general application developer standpoint, I agree with the other answers that there are more important features that rank higher on my list of future enhancements I would like to see.
>
>But from the standpoint of what I do in my current position at TSR, where my main responsibility is this monster data warehouse application known as my "Reporting System from H***", I would do just about anything to have an OOP based report writer. (bg) I can elaborate why I feel that way, but if you get me started I'll just end up hating my job a little bit more ;)

I don’t see the reason why OOP reports is not in the priority list where in a End-User standpoint, REPORTS are the most important thing they want to see in an application. SCREEN designs with all the GUI standards in it, are NOTHING without delivering the required reports. VFP Report Writer is being left behind. One specific example is, you have to run the report twice just to get the total pages so that you could achieve that "Page 1 of 100, etc." in a report, which is awkward. As for menus, there is no direct communication with toolbar buttons, or shortcut menu which to me an important part of the whole application. Yes, I would agree that the above can still be achieved with the current VFP settings but it requires more coding, therefore, tiresome. Or buy third party tools, which again, an additional cost on the part of the user (economics). If VFP is being considered as a RAD tool why no OOP MENUS/REPORTS. To me, application programming begins with MENUS and will end with REPORTS.