I ran across what seems to me like an error with the UltraWinComboEdit control. I'm using the Combo in the "Dropdown" mode and I have set the "Nullable" property to False. In my program I'm moving the Value of the Combo to a string and TRIMMING the Value. Like String1 = comboedit.Value.Trim
Unfortunately, if I select an Item from the Dropdown List, then DELETE the Text, then hit Enter WITHOUT Tabbing out of the Combo, to run the screen io processing, it apparently sets the Value to NULL... and consequently causes a Null reference error which, since I set Nullable to False, I don't think it should do that...
Please note;
If I use the Text property in the program instead of the Value, I have no problem.
If I use the Value property with no value entered into the Combo, I have no problem.
If I use the Value property and Tab out of the field after selecting an Item then Deleting the text, I have no problem.
It's ONLY if I select an Item from the dropdown, then Delete it, then hit Enter and move the Combo value to a string WITHOUT tabbing out of the Combo, that I get the error.
Can you fix that?
This does sounds like it might be a bug. What version of the control are you using? Perhaps you just need to get the latest Hot Fix.
Hey Mike,
I downloaded and installed the latest hotfix. It didn't change anything as far as this problem goes.
In fact, when I looked at the Reference Properties for UltraWinEditors... the runtime version and version were exactly the same as before. Is there something I have to do to "update" my project to incorporate the hotfixes?
Take a look at the Properties for your Infragistics references. In particular, look at the Specific Version property. I suspect that this is set to "true," which would be why your project is still referencing the same version of the assemblies that it was referencing before.
You have two options: