>>A view in the DBC whose source is the SQL tables directly seems better to me in VFP 7 or earlier. I think this is more of a personal preference, than naything. In VFP 8, the CursorAdapter is the cat's meow. How about coming to our next DFW FoxPro User Group meeting next Thursday [Jan 9], and you can ask this question during our open Q & A session. See http://www.dfwfox.org for location, etc.
>
>Thanks for the invite. Unfortunately I was out of town (as seems to be the story of my life). I haven't played with VFP8 yet but I wonder if there are not speed advantages to storing the view in the SQL database.

A view is just the executaion of a stored SQL command to retrieve matching rows regardless of the engine [VFP, SQL Server, Oracle, etc]. So the execution is a wash. All it may do is save you from having to code the INSERT, UPDATE, DELETE to post the changes back to the server. There is no way to get around SQL being used to post changes either whether you do it yourself, the data engine does it or the functionality is coded into IDE [VFP DLLs]. If you do it yourself, you at least have control and can optimize it to the best of your ability and maybe even better than the generic capability built into the DB or IDE.