>Jeff,
>
>>Here's some more data on this issue. I'm using VS2008, SQL Server 2000, and MM .NET 3.5.
>>
>>Here's the trace from the SQL Profiler when I call GetConflictData():
>>
>>exec sp_reset_connection
>>go
>>SET TRANSACTION ISOLATION LEVEL READ COMMITTED;BEGIN TRANSACTION
>>go
>>exec dbo.employeeUpdate @emp_id = 'PSA89086M', @fname = 'Ferd', @hire_date = 'Nov 11 2008 12:00:00:000AM', @job_id = 14, @job_lvl = 89, @lname = 'Afonso', @minit = 'S', @pub_id = '1389'
>>go
>>COMMIT TRANSACTION
>>go
>>exec sp_reset_connection
>>go
>> SET FMTONLY OFF; SET NO_BROWSETABLE ON;
>>go
>>exec dbo.employeeSelectByPK @emp_id = 'PSA89086M'
>>go
>> SET NO_BROWSETABLE OFF;
>>go
>
>I'm not able to duplicate this...is it possible the value of the ConcurrencySelectStatement property has been set in this business object? If it's not readily apparent, I recommend setting a breakpoint in mmBusinessObject.GetConflictData(string tableName, string physicalDbcObjectName, object[] pks, string[] pkFields) to see how it's building the SELECT statement that retrieves conflict data.
>
>Best Regards,

I see what the problem is now. I was using a mmButtonSave save button and had some code in my own handler, but by default the mmButtonSave code to save the data was being called first. I switched out the mmButtonSave button for a plain old mmButton and only my code ran and I could trace through.

However, 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?