Hi Mark,
>>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

>>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>
>>TIA
>
>I don't see that as a conflict because you are updating 2 different fields. The KeyID is only set once and that is at the time the record is inserted into the table. The Updated_By and Last_Update fields always have the user ID of the person who LAST updated the record along with the date/time of the insert or update.

Hmmm, my example was trivial, however, I'm concerned about the general case. Thanks.