Hi Mike,

Thank you for the response and code.  More specifically, I have 4 combo controls.  I will refer to them as c1, c2, c3...  Some event sets c1's datasource = datatable.  The row selected event on all of the combos is set to load a datatable to the next combo in-line.  This code has been in Production for several months, again as a Visual Studio 2008 project and NetAdvantage 9.

Workflow:  User selects a value from c1 and a method is called from c1’s row selected event to set c2, c3 and c4’s datasource to null (to clear them) then c2’s datasource to a new datatable relevant to the value selected in C1.  User then selects a value from c2 and c2’s row selected event calls a method to set c3 and c4’s datasource to null, then c3’s datasource is set to a new datatable, etc.   The user can elect to have values selected in just c1 or all 4 combos.  It depends on the amount of filtering they want to set for an eventual button click to return data to a grid.

So it appears that the row selected event does not automatically fire when the combo's datasource is set in version 9, but now does in v 2011?  If this isn’t the case, I am willing to concede that I have no clue how to properly code this workflow.  Again, what I have has been working perfectly in the Visual Studio 2008 project with 9.2 controls.  I cannot get it to work the same in Visual Studio 2010 and 2011 controls.  My latest iteration is leaving each combo with the previously selected value regardless of what value they select.  It has been one of those weeks... :(

Hi,

I'm afraid you lost me. I understand what you are describing about the 4 dependent combo's. But I am not seeing the behavior you are describing. Setting the DataSource of the combo is not firing the RowSelected event in my testing. Did you try the sample I attached here?

The only time the event fires in my testing is if the Value of the control already contains a value that matches up to something on the new list of values you are binding to.

I'm really not clear on what the problem is or when the event is firing that you think it should not be.

If the user chooses a row from c1 - then I am assuming that c2 never had a DataSource assigned to it at that point. So setting the DataSource to null and then to some actual value should not fire RowSelected. If that's happening, then I would agree that there is a bug there. But I cannot reproduce that behavior.

If the user chooses a new value from c1 after that, then c2 will only fire RowSelected if the existing value of c2 exists on the new DataSource you assign to it.

Are you saying that you are not getting the same behavior I am getting? If so, can you post a small sample project demonstrating this behavior?

Hi,

The problem is the application sits atop a SQL database, so I have attached a non-working project that contains the events and methods straight from the working project that I copied and pasted into Form1.  Detailed notes for you are added to the Form1 code as comments.

Again, this is the code currently in production that works flawlessly as a visual studio 2008 project with the Infragistics 9.2 drop downs.  This same code brought into a 2010 project and switched to Infragistics 2011 controls fails miserably.

Hi Jaime,

I can't run your sample, it won't even compile.This solution does not appear to be valid or complete.

Also, it doesn't appear to be referencing any Infragistics assemblies.

Hi Mike,

I noted that is was a non-working project.  Because the project sits atop SQL I could not quickly assemble a working example for you, but I wanted you to see the methods and events involved that work as a Visual Studio 2008 \ IG 9.2 project, but fails when converted to a VS 2010 \ IG 2011 project.

There are detailed notes as comments in the Form1 code.

Jaime,

Did you try my suggestion?

In the sample that you are referring to try setting the "ItemMatchingMode" property of ultraCombo2 to ValueListItemMatchingMode.DoNotConvertDataValueToString

I was able to quickly reproduce the issue, which turn out to be the same issue just found this morning in my other post "Unexpected behavior changes between 9.2 and 11.2?". 

Michael S.  In your sample, simply change Combo2's .Value member to "State".  Because three of the records have "NJ" as their State, when Combo2 loses focus "Jersey City" is left in Combo2 as the selected record even if you select "Newark" or "Trenton".  This is the smoking gun and does not happen for us in our current production application using 9.2.  Changing the .Value and .DisplayMemeber to "City" is the equivalent of what I need to do to "fix" our upgraded 11.2 application.

I will update the case notes with these findings.  I do not know if it is appropriate to link case numbers in this forum for Mike S. to see, or would it be best for you to attach the sample from the case?

Thank you Micheal S. and Mike S.

This post was elevated to a Support Case, so I now have examples from both of you.  This morning I was able to modify an example for another forum post of mine dealing with a single UltraCombo to reproduce that issue, which looks like the non-unique column I set as the Combo's .Value is causing that issue, which is not an issue with the current production application running 9.2.

I will work on one of your samples now to see if I can replicate this issue with the chained Combos.

Thanks again, Jaime