>>How? In the view, the PK has the value zero, so it is tricky to search for the record. Or do you mean, with requery()?
>
>It's really easy when using a Fox table. The record pointer will be sitting on the newly inserted record.
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.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
