I am joinig this thread late and have not read through all of the answers. IF I am repeating prior comments, I apologize.

I have run into the problem you describe before. I found the view was not set to update the key field in the underlying table. So when the view updated the table the new key value was not passed down to it so the default value function assigned the next #.


>I am using the default framework and basing my view off a joined set of 2 tables. When the view is created, my primary table cust has the proper value, ie next # from table ID. When I do a table update though, the key in CUST is 1 # greater?
>
>v_cust_accnt.custid = 234
>
>cust.custid = 235 for the same record.
>
>Is it because this is a join and it is double pumping the same table in generating id's? accnt.accntid has a different name instead of uid for all the keys.
>
>TIA
>
>__Stephen