In the attached project I have a simple example where I have a DataSet containing a single DataTable which has a single DateTime column.
I then have an UltraGrid bound to this DataSet and the UltraGrid column Style is set to DateTime for the single column that exists. When I run the project and try and use the drop down button to edit the date & time I get:
"String was not recognized as a valid DateTime."
I cannot think of any reason why this may be. I have tried having the default value of the column set to DBNull or an existing date and time. This makes no difference.
Can anyone help?
v9.1 of the controls is no longer being updated, so I ran your sample with v9.2 and it works just fine for me. I suspect that what you are encountering here is a bug that was already fixed.
I recommend that you download the latest service release:
How to get the latest service release - Infragistics Community
Hi,
I have just upgraded to V9.1 from V7.3 and all ultraDateTimeEditor throw ""String was not recognized as a valid DateTime." This happens on all bound dates. The culture is en-AU.The only reason I upgraded was to fix another Infragistics bug. We are just about to release to production and have an expired subscription. Is there a hotfix for this or a workaround? We cant afford to upgrade our subscription.
You could try getting the latest service release.
But judging by the error message, this sounds like a problem with the code. Perhaps you simply have the Visual Studio IDE set to break on all run-time exceptions and this exception is already being handled. Do you get the same exception if you run without the debugger attached?
I think this is a problem with the Infragistics component - after originally starting this thread I upgraded to v10.1 and the problem went away.
When I revert back to v9.1 the problem reappears.
Thanks. Upgrading fixed that problem. However, it has caused another with all our wingrids that call;
this.ScrollColumn(ColScrollAction.Left); this.ScrollRow(RowScrollAction.Top);
on FireInitializeLayout
plus the following throw the same error
this.ActiveColScrollRegion.Scroll(scrollAction); this.ActiveRowScrollRegion.Scroll(scrollAction);
on ScrollColumn and ScrollRow
Exception: "Object reference not set to an instance of an object."
This occurs in the designer and at runtime. Any thoughts?
Stack Trace:
at Infragistics.Win.UltraWinGrid.ColScrollRegion.Clone()at Infragistics.Win.UltraWinGrid.ColScrollRegion.InternalScroll(ScrollEventType scrollType, Int32 lineDelta, Rectangle scrollIntoViewRect, Boolean leftAlign, Boolean takeIntoAccountFixedHeaders, HeaderBase headerBeingScrolled)at Infragistics.Win.UltraWinGrid.ColScrollRegion.InternalScroll(ScrollEventType scrollType, Int32 lineDelta)at Infragistics.Win.UltraWinGrid.ColScrollRegion.OnScroll(ScrollBarInfo scrollBar, ScrollEventType scrollType, Boolean exitEditMode, Boolean invalidateRegion)at Infragistics.Win.UltraWinGrid.ColScrollRegion.Scroll(ColScrollAction action)at SIMS.UI.Controls.MultiBandGridView.ScrollColumn(ColScrollAction scrollAction) in D:\Dev\SIMS\SIMS.NET.root\SIMS.UI\Controls\MultiBandGridView.cs:line 253at SIMS.UI.Controls.MultiBandGridView.FireInitializeLayout(InitializeLayoutEventArgs e) in D:\Dev\SIMS\SIMS.NET.root\SIMS.UI\Controls\MultiBandGridView.cs:line 143at 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.ControlCollection.Add(Control value)at System.Windows.Forms.Form.ControlCollection.Add(Control value)at System.Windows.Forms.Design.ControlDesigner.DesignerControlCollection.Add(Control c)
What version did you upgrade to? Did you get the latest service release or did you just upgrade to a new volume release?
Can you duplicate this exception in a small sample project?
Hi Mike,
I upgraded first from v7.3 to v9.1 which caused the date time bug. To fix that, I upgraded to v10.2. That has now caused the next problem illustrated in the attached sample. (However, did fix the original problem)