>Basically, what VFP seems to be "telling me" with respect to views is that once it populates a view with a set of records, it loses the context of where each record came from in the base table (i.e., the record number), so that you need a unique key to pass updates back to *any* base table from a view. What is happening now is that if I update a field in only one record in the view, *all* records with the same SSN in the base table are equally updated.
>
>By the way, I would appreciate hearing more details about the "WHERE" clause referred to in the Update Panel of the View Designer. Does VFP use the WHERE clause to determine uniqueness of a record in the base table (which has relevance to the problem mentioned above), or to only determine if specific fields have been changed by another user, or something else?
>
>Thanks again.

When you relate 2 tables, you usually are talking about cascade updates, wich means that SQL guides himself by the related key. So if you want to update one single key, you have to have some form of uniqueness in the child table wich are generally all the fields in the tuple.
HTH.
Alex.