Hello all,
Pardon the topic name, but this error has been giving us a lot of trouble and after weeks of investigating we still have no idea how, when, or why it happens.
We use background workers but the grid that's getting this error is independent of the BG.
If someone can please tell us when the error happens so we can trap it, that would be great.
Attached is the error message we're getting when the "Red X" happens.
Thank you very much.
I had a similar problem (different exception, but same red X) in my application. We had multiple threads updating the datasource on a different thread than the main UI thread that the grid was on. We fixed the problem by moving all datasource updates to the same thread as the grid (as Mike S. suggested) using Invoke().
Ok, I created the delegate in the UC and I'm using Invoke to call it. It seems to have stopped the problems but it took a huge performance hit. Is there anything I can do here? Users are now clamoring that they want their speed back...
What can I do?
I have a lot, but I discover that if I use MethodInvoker (Which, I can, because of the function;'s signature) I get all of my performance back. :)
Thanks!
How many rows you got? Since the binding can't be performed in the background, many rows will slow the action.