Hi John,

Firstly, the steps I had sent you were not because VFP supports them this way but because these were usually the situations where I had to use such a view.

>1) You can update both if one-to-one
This one is fairly logical. You would not want to bring invoice header and invoice detail into one view but something like invoice header and customer. Hence a 1-1 relationship.

>2) There has to be a persistant relationship defined (in the DBC I assume)
Again, this probably would not be required but I had this in the example I sent you and the way I have used till now. Though I have not tested it.

>OK...but isn't the solution an example of how you can use more than one VFP feature to overcome the limitations inherent in one? It's still not possible to update more than one table from a view within the context of the View Designer or in code *only* is it?

I sent you a solution and it was not a workaround. The view I sent you was strictly created from the view designer. Though I would say that the view designer has some other problems when you have lots of table involved with different join conditions but that is a totally seperate issue.