>>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 ?
>

There is a signficant bug with the group by clause. Somehow - something that had been working for a long time managed to break in 8. Also, I have encountered a number of C5 errors when XP theme support is on. I'll leave it to you to search the numerous posts that have been made here.


>
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.
>

You have always been able to define views with more complex sql in such a way that would render the view designer moot. You can't say there is a true 2-way tool unless you could define ANYTHING in text - and have it rendered graphically.


>>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.
>

Somewhat gets to my point about cursoradapater - which is kind of like the remote views slightly more sophisticated cousin.


>
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.
>


That may be your impression - but the facts would indicate otherwise. The fact that you clasify the view designer as a true "2 way tool" - I could say the same thing to you. The fact is - the objectional issues that I have articulated about RV's are still applicable today. I have had to deal with RV's extensively. That said - I have used other data access methodoligies extensively. I have had the opportunity to use, evaluate, and compare the various methodologies. While RV's can "work" - but nonetheless - they are inferior to other methodologies out there. Like anything - indvidual milage may vary. That said - when you look at both sides of the ledger - when you look at the big picture - there are far more reasons to eschew RV's than to embrace them. There are 100's of posts over the past 5 years or so from me on the topic. There is no need for me to enumerate those reasons again.