>Given the numerous bugs/things that have been broken in VFP 8 - that is a non-starter.

Like what. I'm not aware of anything major that has been broken in VFP8 ?

>I have looked at the view designer - and most of the improvements come by way of the cursor-adapater - which is a kludge-o-matic way to address the problem.

The view designer does not have anything to do with the cursor adapter class. I'm not sure what you're telling me here. There are a number of improvements in the View designer:

- A true two way definition of views: through the GUI or by entering the view definition by hand.
- It can handle simple views through the GUI of the QD. More advance views that could not be handled (e.g. with subqueries) within VFP7 can be handled within VFP8.
- For complex views you've got the Text part of the querydesigner. You can use the full syntax of the SQL-SELECT to definine the view. though it will not be possible to view thise definition throug the GUI.

In the past I used eview for my view definitions, but that is not neccesary anymore. Most, if not all, view definitions go directly into the view designer. There are a few minor issues with it, but it does not prevent you to be productive and write complex views.

>Perhaps it is true the view designer has "improved" - but the fact remains that the update logic is too closely coupled with the storage mechanism. And - it is a solution that ties you into Fox.

SQL views work with SQL update or SQL Delete and SQL insert. With the cursor adapter you can use anything you want.

>And to be accurate - I did not say I would reconsider my stance on views. Rather, I said I would consider looking at and re-evaluating views if the landscape changed. The landscape has not changed enough for me to change my primary conclusion.

From your reaction I get the impression that you don't have a clue about the improvements in the VFP8 view designer. I get the impression that you don't know what you're talking about.

Walter,