Requery the data behind the scenes. The user won't know it's happening.

>
>I tried it, and this works great - to get the primary key back into the view. This may help in some circumstances (like, saving data for child-tables, related to the view in question). But unfortunately, it doesn't solve my original problem: if a new record is saved, and then immediately edited and saved again, I still get an update conflict. I assume that Visual FoxPro checks for oldval("pk"), and that is zero.