Juan,

Actually, you can use the standard StrataFrame soft collision form with row versioning or timestamps just fine. If I remember correctly it used to only work with OptomisticAllFields, but we changed it to work with all 3 standard methods a while back.

Have you tried setting up a test with row versioning? If not I'd do that if you are running into issues. Isolating the concurrency handling into a little one form test app would probably be the easiest way to better understand how all of that works under the hood. If you run into any problems getting it set up, just give us a shout and we'll be happy to guide you through any rough spots .

Hi Dustin



I did that test with the 1.6.5.3 (I use the beta of last month, the last two no, because I use DevExpress controls to the last version and there are not sources in the downloads section, for recompile).



After add a RowStamp column (integer) and setup the Nulls as needed and make this changes in the BO:



ColissionNotificationType: RaiseEvent

RowVersionOrTimeStampColumn: RowVersionColumn (the name of the column in my table)

UpdateConcurrencyType: OptimisticRowVersion



After that I run the app from VS 2008, goes to the form, enter in EditMode and change a value. Also run the exe from Debug directory (at the same time) goes to the form, in the same record also enter to edit mode and change the same value but with different information. The save the first one, and when save the second nothing happens (when doing this using the default concurrency, the Windows of SF comes up. If I close the form and reopen the record is updated to the value that was saved first.



Also I changed the ColissionNotificationType to ThrowException and make the same thing, and yes when I save form the second running application, it presents the error window. That's why I supose the SF only present the colission window for OptimisticAllFilds.



Sure I miss something, hope you can give me some ideas?



Regards

Everything is possible, just keep trying...

No problem, we'll get to the bottom of it

First be sure that you open the second instance before you change the value, otherwise you aren't getting a collision detection. Based on it throwing the exception when you change the notification type, however, it sounds like you are doing that correctly.

The only other thing to check is that the AutoHandleCollisions property of the Form is set to True, which is the flag that determines whether or not to show the soft collision form.

If that appears to be set up correct, try reproducing the collision with the attached sample project. Just point it to your StrataFrameSample database when it asks you for connection information. It is configured to use row versioning and should display the soft collision form when you run it through the collision scenario.

Let me know whether the test app works and we can go from there

Dustin



Thanks for your help, ¡It's working now!



I go back and add the RowColumnID (Int, Not allow nulls), configure the BO and test my form and works. I think the problem the first time I did is that not define Not allow nulls, I use the BO Mapper to handle this, of course don't do it well.



Thanks a lot for your help.



Regards

Everything is possible, just keep trying...

No problem at all! Glad you got it working