I'have updated my project from 2013.2 to 2014.1.
My OptionSet is placed in a user control and bindings where set by code at runtime (load-event of the user_control).
this.OptionUnit.DataBindings.Add( "Value", this.bsAccProp, "AccUnit" );
This worked fine. But with version 2014.1, no value of the option set looks selected anymore!! At binding time, the data are not loaded into the dataset where the binding source bsAccProp is using.
I have figured out that If I move the code above after data is loaded into the underlaying data set, the option set works like expected.
This is an very bad change in the behaviour of the option set control and you are lucky to check it out. What is the reason for this? Do I miss something here?
Regards, Markus
I'm pretty sure this is a known bug and is fixed in the latest service release. If not, then it will be fixed in the next one, which is due to release next week.
I have found the problem. Relax, it seems to be a application bug. The unerlying data type has changed in the application. The OptionSet datavalue of Type Int16 was bound to application data of type BYTE.
I'm pretty sure that the application data types has not changed recently, so the "tolerance" about this mismatch in OptionSet control has changed maybe after updating to version 2014.1 (the control raised no exception).
Thank you Mike and Michael for answering.
Regards
Markus