We have a banking application that we are working on that has several wingrids in it.It works fine when we pull the first account. But after we close that account and open another one, the app locks up. When I Ctrl+Break it shows to be on the databind line of various datagrids. I have tried the MaxBandDepth suggestion but that doesn't seem to help.
Any ideas?
Thanks,Kevin
Are you using a BindingSource as your Datasource? This was once a recommended practice especially for multibanded grids and I believe it still holds true. I imagine Mike will be along with a comment to verify this.
Nick
Yes I remember seeing the suggestion about using a binding source. I'm using binding sources for everything.
Noticed this morning that it also locks up sometimes on the InitializeComponent().
I've been meaning to trace my application using something like RedGate ANTS profiler to see if I can find something. I just haven't gotten around to doing it yet.
Neither the grid nor the BindingManager in DotNet are thread-safe.
Work with a dataset bound to a grid on a separate thread - Infragistics Community
OMG. I didn't realize that you were using threads. Yes that would definately be a problem. I've changed my coding style so that if I ever have to do anything like talk to a server or do something that takes a long time I don't interface with the grid or the data it's bound to until I am back in the same thread.
We've figured it out.
Turns out that the Ultragrid's Databind is not thread safe...
We have tracked it down to one specific control.The control has 3 different ultragrids with 3 different datasources.Only one of the 3 is visible and even loaded and databound when the form is opened, depending on the type of account.