I guess I spoke too soon. I was able to reproduce the problem using one of their sample applications but they say they can’t reproduce it on their end and sent me back a sample application to try. The sample they sent populated the UltraComboEditor directly and I was able to run it with no errors. It appears that the control must be bound to cause the error. I created an updated sample and sent it back to them and I’m still waiting for a response. They are no where close to providing the level of service that you guys do The sample is simple, just an UltraComboEditor on a standard Windows form with the following code in the form’s load event.
Private Sub Form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
Dim letters = New String() {"B", "A", "C", "E", "D"}
Me.UltraComboEditor1.SetDataBinding(letters, "")
End Sub
Using that sample produces a null exception if SortStyle is set to anything other than “None” when run against 2006 Vol 3, Vol 2 runs okay. If you guys have priority support with them you might try to see if you can get them to look at it. Since 2007 Vol 1 just came out I recompiled the SF wrapper for that version and so far everything looks okay.
-Larry
And, no, I don't think we have priority support, sorry, we have to wait in the same bucket as you do.
I just received another reply from Infragistics tech support saying that they cannot reproduce the error. Since I haven’t seen any postings here of a similar error, maybe it’s something in my environment. I tried uninstalling vol3, downloaded a new copy, re-installed and still received the same error. However since you were able to reproduce it using their standard distribution but not against their compiled source code I’m assuming that it’s something in the distribution or installation. Since 2007 vol 1 seems to be functioning normally I’m going to forget about 2006 vol3 and move on.
For anyone else that may have experienced this problem, Infragistics was finally able to reproduce it. Installing NetAdvantage HotFix 6.3.20063.1059 fixes it.