>>>>>It's been requested often, so they won't hear anything new. In fact, I'll wager that the most common requests are:
>>>>>
>>>>>- OOP Reports
>>>>>- OOP Menus
>>>>>- Fix the view designer
>>>>
>>>>I know, but the problem I have is this. It is broke! The report designer and menus may be old hat, but they work. The view designer is broken, bad, full of holes, causing problems, limited in use, etc.. If I put out code here like that I would not be programming too long.
>>>>
>>>>What makes me feel somewhat better about it is that ACCESS's view designer is just as bad.
>>>
>>>I don't know if it's broken, in as much as it wasn't designed completely. IMO, broken means it doesn't work. The view designer *does* work...just not very well. I've already sent my request to the Fox team that they not only fix the view designer, but they make it replaceable, like the Class Browser and many of the other tools. Think about it. There is an _VIEWDESIGNER variable that points to the tool you want to use, and VFP autmatically uses it.
>>
>>That sounds good. The added flexability would sure enhance the product. But I still disagree with the 'Broke' definition. But I think we can agree to disagree as long as we work on getting MS to address the issue.
>
>Can MS take a look at the EView and incorporate its best features?

I am sure they are getting suggestions from the code and the author.