>I have MS-SQL assigning a unique identifier as a primary key in the back end. I'm linking to the tables via remote views. My problem is when I save an Added record I don't have the primary key yet so if the user makes an immediate change on the added record an update conflict error occurs. I can do a REQUERY() after the save, but this seems alot just to get the primary key back to the front-end and the Refresh() function won't work as far as I can tell. I'd like to hear what you all are doing in this case.
>
>Thanks in advance.

I use a separate table to handle the counters for IDs. There are many problems with using indentity fields. It is just safer and more flexible to assign the keys yourself.