hi,
having a really strange problem...not seen this problem before..and ive used winultra grids for awhile now. I have a main form set with a ultragrid displayed on it...when i call a dataset from a storeprocedure and ask the datagridview to display the data, it works perfect. However...when i click the scroll button to scroll down the data...it crashes my application with the following exception:
Cross-thread operation not valid: Control 'ultragridview1' accessed from a thread other than the thread it was created on.
any ideas?this is happening on all my applications im working on using ultragrids.
thanks
EDIT: since googling the error..its apprently a threading problem..this code is not using threading
This definitely appears to be a threading issue. Are you sure your code is not using multiple threads?
Also, are you using the UltraWinGrid here? You mentioned the DataGridView, which is not the same control.
If this is, in fact, an UltraWinGrid, and you are certain that your application is not using multiple threads, then your best bet is to try to reproduce the issue in a small sample project and Submit an incident to Infragistics Developer Support so they can check it out.
hi mike, yeah..its occuring on every application im using now...which involves ultrawingrid..i'll try a reinstall of infragistics.
You should make sure you have the latest Hot Fix and if that doesn't help, Submit an incident to Infragistics Developer Support so they can check this out.
where can i download the hot fix?
My Infragistics Keys and Downloads - Download Anything and Everything You Own
Mike,
I'm having the same cross-thread scrolling issue with my UltraGrid in a non-multithread application. I have an older version (Netadvantage 1.2 ?) of your product. Has this been resolved?
Thanks.
George
We resolved our problem by appling all .NET service packs. As I remember, we had to update .NET 3.5 because it had embedded updates for .NET 2. After the updates all our customers reported no further issues with scrolling. However, the scrolling issue during debugging via Visual Studio still remains.
kmg,
Thank you so much for responding. I have noticed that the issue seems to occur solely while debugging in the development environment. Really troubling after so much work. But my experience is similar to yours - no apparent problem (yet?) in the production version. Thanks again for responding.