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,