Jump to content
Software FX Community

Confirmation of fix to 'Not a legal OleAut date' exception

User (Legacy)

Recommended Posts

I'm using Chartfx for Windows Forms .net to display a Gantt chart with

DateTime values.

In the following old versions of ChartFx:

c:\temp\rtm\old\chartfx.dll Version 6.2.1342.0 (6.2.1662.18864) 20-Jul-2004


c:\temp\rtm\old\chartfx.base.dll Version 6.2.1342.0 (6.2.1662.18828)

20-Jul-2004 10:27:46

c:\temp\rtm\old\chartfx.borders.dll Version 6.2.1342.0 (6.2.1662.18841)

20-Jul-2004 10:28:04

I get the an exception when the chart is zoomed and I move the mouse over

the chart bars to get a tooltip (I do get my custom tooltip ok though):

System.ArgumentException: Not a legal OleAut date.

at System.DateTime.DoubleDateToTicks(Double value)

at System.DateTime.FromOADate(Double d)

at SoftwareFX.ChartFX.23.T1(Double 2Q2)

at SoftwareFX.ChartFX.ValueFormat.M9(Double 29W, CultureInfo 29X)

at SoftwareFX.ChartFX.ValueFormat.FormatNumber(Double d)

at SoftwareFX.ChartFX.1S.GetInfoString(PaintMarkBase pms, String mask,

HitType hitType, Int32 nSeriesInfo, Int32 nPointInfo, GetInfoStringFlag

flags, Object tag)

at SoftwareFX.ChartFX.0Y.GetString(UIString nType)

at SoftwareFX.ChartFX.0V.4C(Point 1V5, String& 1V6)

at SoftwareFX.ChartFX.J.5C(Object 166, EventArgs 167)

at System.Windows.Forms.Timer.OnTick(EventArgs e)

at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr

idEvent, IntPtr dwTime)

When I upgraded chartFx to the latest version:

c:\temp\rtm\new\chartfx.dll Version 6.2.1342.0 (6.2.1754.19545) 20-Oct-2004


c:\temp\rtm\new\chartfx.base.dll Version 6.2.1342.0 (6.2.1754.19496)

20-Oct-2004 11:50:04

c:\temp\rtm\new\chartfx.borders.dll Version 6.2.1342.0 (6.2.1754.19521)

20-Oct-2004 11:50:44

And run the same application, the problem goes away.

Clearly the answer is to use the latest version of ChartFx.

Can you confirm that ChartFx has done some code change to resolve the 'Not a

legal OleAut date' exception? I need a positive confirmation for my users

that the problem is fixed, rather than it just went away.



Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...