>>>Hello all....

>>>What is a proper way to update both parent and child table with one local view? or is this not possible...

>>>Thanks.

>>In general, table maintenance such as this is best done from a trigger. This will ensure that any changes made anywhere (other forms, browse windows, etc.) in your application will always be transferred to to the child table. If you are also updating the parent table from the child table you may, however, run into problems with recursions.

>Yes I've thought about triggers as well, but I want to avoid triggers as much as possible for speed.

A trigger wouldn't be any slower than using a view. I would tend to think, in fact, that it would be faster.