>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 #.
>

---

Follow the thread to the last or second to last message. There is a fix described in changing a property in the framework. The proper fix is using the EVAL() function. Sorry I can't remember it exactly, but it's the cure!

__Stephen