>I've got a view that can update 2 tables. Updates of existing records work fine, but every time I insert a new record into the view and do a tableupdate, a record gets added into both tables.
>
>The view is defined with optimistic table buffering. One of the 2 tables is primary. A new record in this table will always reference an existing record in the other (secondary) table, the way my app is designed. The one field in the secondary table I want to update is a foriegn key reference to the primary table.
>
>In order to implement this functionality, must a break the one view up into two views?
>
>Seems like you aught to be able have a multiple table update view that doesn't always add a new record to all updatable tables on a view insert -- or am I missing something?
>
>TIA
>
>Doug


Doug, Is the Referential integrity set so that inserting a new into one inserts a new into the other?