Vlad,

Thanks. I will be breaking my view up into 2 separate views, as you suggested.

I'm using a framework (Mere Mortals) which does the transaction management and tableupdates for me, so I don't want to change the cursorSetProps, since it would be difficult to weave the changing of the properties with the framework's code.

In my old approach I inserted a view record with the primary key of the secondary table set to an existing record from its base table. I was thinking/hoping that this action would defeat the inserting of a new record in the secondary table at tableupdate. However, if I set the secondary table's primary key to not updateable a new record is added (to the secondary table) with a newly generated primary key. If I mark the secondary primary key as updatable, I get an error when a record with an already used primary key is inserted.

Anyway, thanks again. I think I now have an approach that will work for me.

Doug