Hi Mark,
>You may use the code as you wish. There is nothing proprietary or secret about any of the Oracle code. I do not update or set values for the KeyID, Updated_By and Last_Update fields. My triggers handle this entirely. Since I do not update these fields, how Oracle handles the setting of the values for these fields has no bearing on update conflicts on other fields.
>
>The only way an update conflict can occur, is if another user changes a value in a field other than those 3. If you decide not to issue the update and do not force the update, no field values change including those 3.

Thanks,
Sorry if I'm being dense, but one more time on the Update Conflict issue...
Say I have a table with the following fields:

KeyID
Updated_By
Last_Update
FirstName
LastName<\PRE>
If User1 changes FirstName and User2 changes LastName, Key and Modified would miss the conflict.  (This IS a problem in the VFP version)  Key and Timestamp (in SQL Server) would deny the update.  Using Key and Updatable can create a string that is too long.  Am I clear this time? <G>

Bill Armbrecht
VFP MCP