>Hi All,
> I just wanted to run something by everyone. I as most other people have a list of new features that I want to see in the next versions of VFP. There are two features though that I am not so sure make it to the top of my list like they might for other people here.
>
>These two features are OOP Menus and OOP Reports. I am not so sure what the big benefit to these features would be so I wanted to run it by this group.
>
>So here are my questions
>
>1.Are OOP menus and OOP reports important to you ?
>
>2. If you answer yes, WHY ?
>
>3. If you answer no, WHY NOT ?
>
>
>All answers are appreciated.
>
>
>Rod


Recently I wrote an application that required generating a table (number of columns) out of user input. Some of the cells on the grid needed to be painted in different colors depending on its attributes and, one of the main requirements was that the grid had to be printed. I posted to problem several months back and got many replies trying to help, but nothing worked, I even called the MSFT engineering dept. and they said that for future versions they may have it (?). I almost abandoned the project until a friend helped me create a report from scratch. By creating the objects by code (all the cells) programatically, he was able to generate the frx needed for the report. That way I was finally able to add a printing feature to my app. This could've been avoided by having a WYSIWYG feature on the report writer.

Count me in as a oop-report writer supporter.

And with menus the same story goes. With so many applications sharing information such as e-mail, printing features, customizable button bars, etc. there should be an oop menu writer. It'd make life better for us.

There you go.

Gil