Wow, i also see the text area on your website for posting replies do not even keep linefeeds, pretty sad, should maybe tell webmaster about that one...the error info from call stack was placed a few lines below the rest, but the textarea removed all spacing and now everything is stuck together, yuk!

Sorry typo, meant to say Mike, but your website has no edit post possibility, so could not correct this typo.

Thank you for the quick response Miie, here is what I have ... I have the red x wthin my grid... As soon as I finish firing this method below I get the error, and this method fires during the initial showdialogue call to the window Private Sub ugResult_InitializeLayout(ByVal sender As System.Object, ByVal e As Infragistics.Win.UltraWinGrid.InitializeLayoutEventArgs) Handles ugResult.InitializeLayout e.Layout.Override.CellClickAction = CellClickAction.RowSelect If Me.MultiSelection = True Then e.Layout.Override.SelectTypeRow = SelectType.Extended Else e.Layout.Override.SelectTypeRow = SelectType.Single End If End Sub Also, when I call the window the first time, it has the problem in question, but when i close the window, and make the same call to the same window, the window has no more bug, it is like because it was loaded the firt time, there is left over code (either garbage collector hasnt passed) which makes the window appear without bugging...weird! Aside from this, if i unbind the grid from its datasource (read this somewhere) i do not get this error here, it loads normally, but then i end up with a red x in my grid later when i try to use grid.datasource = mydatasource call... As for the actual error...here is the error info(something to do with the gridbaglayout manager ...?) Thanks in advance....! System.ArithmeticException was caught Message="Overflow or underflow in the arithmetic operation." Source="Infragistics2.Win.v7.3" StackTrace: at Infragistics.Win.Layout.GridBagLayoutManager.GridBagHelper(ILayoutContainer container, Object containerContext, Boolean layoutContainer, Boolean returnItemDimensions) at Infragistics.Win.Layout.GridBagLayoutManager.GetLayoutItemDimensions(ILayoutContainer container, Object containerContext) at Infragistics.Win.UltraWinGrid.UltraGridBand.VerifyRowLayoutCache() at Infragistics.Win.UltraWinGrid.UltraGridBand.CalculateBandMetrics(UltraGridBand priorBand) at Infragistics.Win.UltraWinGrid.BandsCollection.CalculateBandMetrics(Int32 pass) at Infragistics.Win.UltraWinGrid.BandsCollection.CalculateBandMetrics() at Infragistics.Win.UltraWinGrid.ColScrollRegionsCollection.InitializeMetricsHelper() at Infragistics.Win.UltraWinGrid.ColScrollRegionsCollection.InitializeMetrics() at Infragistics.Win.UltraWinGrid.UltraGridLayout.ApplyLoadedBands() at Infragistics.Win.UltraWinGrid.UltraGridLayout.ListManagerUpdated(BindingManagerBase bindingManager) at Infragistics.Win.UltraWinGrid.UltraGridLayout.ListManagerUpdated() at Infragistics.Win.UltraWinGrid.UltraGridBase.Set_ListManager(Object newDataSource, String newDataMember) at Infragistics.Win.UltraWinGrid.UltraGridBase.VerifyDataSourceAttached() at Infragistics.Win.UltraWinGrid.UltraGridBase.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow) at System.Windows.Forms.Control.SetVisibleCore(Boolean value) at System.Windows.Forms.Form.SetVisibleCore(Boolean value) at System.Windows.Forms.Control.set_Visible(Boolean value) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) at System.Windows.Forms.Form.ShowDialog() at Offix.Ecran.EcranBase.ShowDialog()

Hi,

A red X indicates that the something threw an exception during the grid's (or any controls) OnPaint method.

The most common cause of this kind of error is a threading issue. Is your application using multiple threads?

The exception message you listed seems to indicate some kind of math error. So I suppose this could occur if you are using images in your grid and those images are extremely large.

Another possibility is that the exception is being raised by some code in your application and it's not showing up in the right place because it's being caught and handled. This will happen in certain event handlers. So you might want to try setting Visual Studio to break on all run-time exceptions and see if it will take you to a specific line of code.

There's no event that fire when the grid's data binding has completed after InitializeLayout, because DataBinding is never complete, it's an ongoing process. If you can post the call stack from the exception, that might provide more of a clue.

I have gained some ground, i think, I now know from certain debugging traces and reading a few places what the error pertains to, and the grid is bound to a datasource, and if i unbind the datasource right before i call showdialogue, then i do not get this error, but whenever later on i try to reattach the same datasource, i get an error which is the arithmeticexception error i stated previously. Anyone have any ideas...?