>Jeff,
>
>>I still have not gotten an answer regarding how the Concurrency works. I cannot get it to work as advertised in the Dev Guide. Can you help me understand this?
>>
>>I still have the problem where if I bring up my WinForms form with first name coming from Pubs.employee as 'John' and then behind the scenes in Query Analyzer I change that to 'Joe' in the table and then in my form change it to 'Jim' I don't get the concurrency error that the Dev Guide shows under the 'Handling Concurrency Error' section.
>>
>>Should the concurrency dialog come up?
>>
>>Can you show me how this is supposed to work?
>
>Oops...I missed that! If you are using stored procedures to update data, you need to add a Timestamp column to the associated table so that ADO.NET raises a concurrency exception. The MM .NET Business Layer Generator automatically adds the Timestamp column to the WHERE clause of the UPDATE stored procedure.
>
>Best Regards,

Kevin,

There also seems to be a related problem when you use Timestamp columns to detect a concurrency exception. The concurrency exception dialog does appear as expected, but you cannot choose to overwrite the existing data with your data. Or rather I should say if you choose to do that, your data will never be saved.

Sam