I have a BO where I select some additional fields from another table in a custom fill method to populate some custom fields. I'm using stored procedures that were automatically created by DDT to handle the inserts and updates. I'm also using Optimistic Timestamp for concurrency. When I run a single instance of the application everything works fine. However when I run two instances and enter updates that are designed to cause a concurrency violation, the second instance to call save gets an unhanded exception during the save. The inner exception lists the added fields as invalid column names. I haven't traced the code (since I don't have the v1.61 source) but I'm wondering if the code that handles concurrency issues is using the column names from the data table rather than the AllFieldsList. I also tried adding the additional column names to the FieldsToExcludeFromInsert & Update but still get the same error.

-Larry

We are going to take a look at the other post....sorry we missed it

Yep, just fixed it, Larry... I also changed the comparison of the field collisions to ensure that only columns that exist in both the retrieved server row and the local row are compared for a possible field collision.  Will be included in final 1.6.1 release.