I have a master table that has one record per person. Each person is identified uniquely by their social security number (SSN). I have a child table that has zero or more (up to about 10) line items per person. Each of these items uses SSN as the key to relate back to the person in the master table. However, the child table does not have a unique key for each record. When I create a view on the child table, selecting all records for one SSN, I am having trouble passing the update back to the child table. What happens is that all records with the same SSN in the child table are updated with the info from only ONE updated record in the view. VFP warns me about this, saying that the key is not unique. The child table is huge. How do I optimize the updates for the child table (using a view of that table). I know that rebuilding the child table with a unique key will work, but that's a major hassle. Is there another way? Thanks!