Views are good, but I would never have a single view that updates multiple tables. One view per table. Additionally, I never allow the user to enter the primary keys. Surrogate keys solve the problem.
>Hi All,
>
>In a view that contains a relationship between two tables, my intention is that when the key field on the main table is changed, the view changes its display in the child table to update data pertaining to the changed key field, or none at all, if there is no such similar field. However, this is not happening, and the data in the child table displays the same original data. Could somebody help?
>
>This could be just out of the VFP starter kit, but I do not use views too often, preferring to use tables directly in the dataenvironment.
>
>Regards,
>
>Steve.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer