Tamar,

I agree with you and Alex. There's a major difference between limitations (e.g. report designer) and the view designer which has the potential risk to destroy a working view by simply opening it.

>The reason a hook would be useful is that, then, the program you specify would be called when you issue MODIFY VIEW or when you Modify a view from the Project Manager. It would solve the problem of accidentally ruining your view because you open it in the VD.
>

Adding the hook would avoid above problem, but I still believe it's unacceptable in a database development tool to have no usable view/query designer. Again, one reason why I insist is because I believe it shouldn't be too hard to fix it (as opposed to other items on the wish list such as OOP reports/menus). It works in any other MS tool...

If you think about MS Access, one of the reasons why it's so popular among database novices is because the query/view designer is quite easy to use. As Alex said, if you have new VFP users, this can make a big difference.

I do most of my view/queries by hand, but only because I have no other choice. It sure is much easier to select fields and join tables using a graphical user interface. And if the designer is 2-ways or 3-ways like in SQL Server, you get the best of each.

>That said, sure, I'd rather that Microsoft gave us a usable View Designer. But, if for some reason, we can't have that, it would at least be useful to be able to keep the awful one from breaking our views.
>
>Tamar