A
andrew allan
I was trying to use excel as a math engine in a VB.NET application.
I used the following code snippet
Dim xL As New Excel.Application
Dim B As String
MsgBox(xL.Evaluate(B).ToString)
This works as long as the string value parsed to EXCEL doesn't exceed a
certain length (i.e. the string "AVEARGE({0,1,2......,82,83,84})"
worked. The string "AVEARGE({0,1,2......,82,83,84,85})" fails and gives
me the result -2146826273.
However when the same strings are used in the native EXCEL environment
they seem to work just fine.
I am using Visual Studio.NET and have loaded a references to both the
EXCEL 10.0 and OFFICE 10.0 object libraries.
I need to parse sets of data which may contain upward of 100 points, and
am interested in doing some further statistical manipulation on them
(such as percentiles, standard deviation etc). Does any one have any
suggestions on how I can get over this seeming limited string
caapability.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I used the following code snippet
Dim xL As New Excel.Application
Dim B As String
MsgBox(xL.Evaluate(B).ToString)
This works as long as the string value parsed to EXCEL doesn't exceed a
certain length (i.e. the string "AVEARGE({0,1,2......,82,83,84})"
worked. The string "AVEARGE({0,1,2......,82,83,84,85})" fails and gives
me the result -2146826273.
However when the same strings are used in the native EXCEL environment
they seem to work just fine.
I am using Visual Studio.NET and have loaded a references to both the
EXCEL 10.0 and OFFICE 10.0 object libraries.
I need to parse sets of data which may contain upward of 100 points, and
am interested in doing some further statistical manipulation on them
(such as percentiles, standard deviation etc). Does any one have any
suggestions on how I can get over this seeming limited string
caapability.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!