Hello all,

There is a minor bug in the way the toolstrip buttons get enabled/disabled.  To recreate the issue follow these steps:

1. Compile and run the SampleCRMApplication
2. Launch 2 Customer Maintain Forms
3. Click Browse and select the same data sets on both forms
4. With the maintenance forms open, change the same record on both (IE. Change Catherine Abel on form 1 to Katherine Abel, Form 2 change her first name to Kathy)
5. Save on Form 1.  No issues
6. Save on Form 2
7. You are prompted with an optimistic concurrency error window which is correct
8. Click the Cancel Save button

Notice now on Form 2 the Browse, New, Edit, Delete, Save and Undo buttons have been enabled.  Shouldn't the Cancel Save put the user back to a "Save/Undo" state only?

Ben Kim
 

Can you please confirm this issue?  I want to ensure it has nothing to do with my environment.

Thanks!

Ben

No, we were able to reproduce it on this end... when you cancel the saving through the concurrency exception event, the Save() method does not properly return a value other than Success, so the business object's editing state is set back to Idle, causing the controls to disable and all of those menu items to enable, but the business object is still dirty, so the Save and Undo are enabled as well.  We changed the DataLayer class to prevent Success from being returned when the save is canceled by that form.