Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our group. It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we show
in our app. In our application we several areas where we have to take a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this generates the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException: Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo info)
at System.UInt16.Parse(String s)
at ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line 357
In other parts of the application, we may be using the string in a different
way(ie. we use the string/convert it to an int and use it as an index), and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line 1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line 1052
We know it has something to do with having a "0" in a string, but have NO
idea, of why it happens on only some of the machines and not all (luckily I'm
not one of the problem machines), and also why it works with 1.1 version of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start looking?
My apologies for the length of the post. Thanks in advance for any help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
8  2089 
WhiteWizard <Wh*********@discussions.microsoft.comwrote:
Have we got a STRANGE one going here.
I have difficulty understanding what your problem is. You're calling
ushort.Parse() with a string, and it isn't a valid string, right? So
panels / viewing areas and related discussion etc. is irrelevant, right?
What exactly is the problem?
at System.UInt16.Parse(String s)
at ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
The code that's calling Parse is under your control - surely you can
isolate the value that's being passed to ushort.Parse()?
-- Barry
-- http://barrkel.blogspot.com/
Hi,
You have some error in the format of the number, can you post the code in
question?
Also compare one working machine and one with the error regarding the
culture being used , especifucally the NumberFormatInfo benig used.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:9A**********************************@microsof t.com...
Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our group.
It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we
show
in our app. In our application we several areas where we have to take a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this generates
the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException: Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line 357
In other parts of the application, we may be using the string in a
different
way(ie. we use the string/convert it to an int and use it as an index),
and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style,
NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object
sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1052
We know it has something to do with having a "0" in a string, but have NO
idea, of why it happens on only some of the machines and not all (luckily
I'm
not one of the problem machines), and also why it works with 1.1 version
of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start looking?
My apologies for the length of the post. Thanks in advance for any help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
Ok, so I obviously didn't get the message out ;) I HATE it when that happens!
The problem is that WHENEVER we have a string with a value of "0", we have a
problem. The errors we just examples of some of the problems. And it
appears that it ONLY happens when the value of the string is "0".
We did check the versions of the framework we are using, but have NOT
checked the NumberFormatInfo as suggested, so I'll do that today.
Thanks for the responses!
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Barry Kelly" wrote:
WhiteWizard <Wh*********@discussions.microsoft.comwrote:
Have we got a STRANGE one going here.
I have difficulty understanding what your problem is. You're calling
ushort.Parse() with a string, and it isn't a valid string, right? So
panels / viewing areas and related discussion etc. is irrelevant, right?
What exactly is the problem?
at System.UInt16.Parse(String s)
at ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
The code that's calling Parse is under your control - surely you can
isolate the value that's being passed to ushort.Parse()?
-- Barry
--
http://barrkel.blogspot.com/
I have good news and bad news.
The good news is that with Ignacio's suggestion we checked the
NumberFormatInfo parameters and found that for the problem machines the
PositiveSign Value is a 0, but only for en-US and only on the problem
machines.
I also verified that this is what was causing the problem by temporarily
changing my value to a 0 and got the errors.
The bad news is I cannot find any way to change the value back to a + sign
as it is on the non-problem machines and for all other culture settings. I
also have no idea HOW the bad ones were set to 0 in the first place.
I found where you can change how the system treats negative numbers, but
nothing so far on setting the PositiveSign value. Has anyone seen this
before, or can anyone tell me how I might change the PositiveSign value?
Thanks for your responses earlier. It definitely helped us isolate the
problem.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Ignacio Machin ( .NET/ C# MVP )" wrote:
Hi,
You have some error in the format of the number, can you post the code in
question?
Also compare one working machine and one with the error regarding the
culture being used , especifucally the NumberFormatInfo benig used.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:9A**********************************@microsof t.com...
Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our group.
It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we
show
in our app. In our application we several areas where we have to take a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this generates
the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException: Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line 357
In other parts of the application, we may be using the string in a
different
way(ie. we use the string/convert it to an int and use it as an index),
and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style,
NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object
sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1052
We know it has something to do with having a "0" in a string, but have NO
idea, of why it happens on only some of the machines and not all (luckily
I'm
not one of the problem machines), and also why it works with 1.1 version
of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start looking?
My apologies for the length of the post. Thanks in advance for any help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
Hi,
One of the Parse variants takes a NumberFormatInfo you can use it. The weird
thing is that you say that you get error not when you have a '+' in front
but when you have a 0 , so +1 is ok, , but 01 which is kind of weird.
why don't you try with this version and use InvariantCulture as the
parameter.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:73**********************************@microsof t.com...
>I have good news and bad news.
The good news is that with Ignacio's suggestion we checked the
NumberFormatInfo parameters and found that for the problem machines the
PositiveSign Value is a 0, but only for en-US and only on the problem
machines.
I also verified that this is what was causing the problem by temporarily
changing my value to a 0 and got the errors.
The bad news is I cannot find any way to change the value back to a + sign
as it is on the non-problem machines and for all other culture settings.
I
also have no idea HOW the bad ones were set to 0 in the first place.
I found where you can change how the system treats negative numbers, but
nothing so far on setting the PositiveSign value. Has anyone seen this
before, or can anyone tell me how I might change the PositiveSign value?
Thanks for your responses earlier. It definitely helped us isolate the
problem.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Ignacio Machin ( .NET/ C# MVP )" wrote:
>Hi,
You have some error in the format of the number, can you post the code in
question?
Also compare one working machine and one with the error regarding the
culture being used , especifucally the NumberFormatInfo benig used.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:9A**********************************@microso ft.com...
Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a
problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our
group.
It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we
show
in our app. In our application we several areas where we have to take
a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this
generates
the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException:
Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line
357
In other parts of the application, we may be using the string in a
different
way(ie. we use the string/convert it to an int and use it as an index),
and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style,
NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object
sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1052
We know it has something to do with having a "0" in a string, but have
NO
idea, of why it happens on only some of the machines and not all
(luckily
I'm
not one of the problem machines), and also why it works with 1.1
version
of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start
looking?
My apologies for the length of the post. Thanks in advance for any
help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
You should be able to change them in the registry at
HKEY_CURRENT_USER\Control Panel\International
or
HKEY_USERS\.DEFAULT\Control Panel\International
The value your looking for is sPositiveSign. It is set to an empty string on
my machine
/claes
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:73**********************************@microsof t.com...
>I have good news and bad news.
The good news is that with Ignacio's suggestion we checked the
NumberFormatInfo parameters and found that for the problem machines the
PositiveSign Value is a 0, but only for en-US and only on the problem
machines.
I also verified that this is what was causing the problem by temporarily
changing my value to a 0 and got the errors.
The bad news is I cannot find any way to change the value back to a + sign
as it is on the non-problem machines and for all other culture settings.
I
also have no idea HOW the bad ones were set to 0 in the first place.
I found where you can change how the system treats negative numbers, but
nothing so far on setting the PositiveSign value. Has anyone seen this
before, or can anyone tell me how I might change the PositiveSign value?
Thanks for your responses earlier. It definitely helped us isolate the
problem.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Ignacio Machin ( .NET/ C# MVP )" wrote:
>Hi,
You have some error in the format of the number, can you post the code in
question?
Also compare one working machine and one with the error regarding the
culture being used , especifucally the NumberFormatInfo benig used.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:9A**********************************@microso ft.com...
Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a
problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our
group.
It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we
show
in our app. In our application we several areas where we have to take
a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this
generates
the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException:
Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line
357
In other parts of the application, we may be using the string in a
different
way(ie. we use the string/convert it to an int and use it as an index),
and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style,
NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object
sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1052
We know it has something to do with having a "0" in a string, but have
NO
idea, of why it happens on only some of the machines and not all
(luckily
I'm
not one of the problem machines), and also why it works with 1.1
version
of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start
looking?
My apologies for the length of the post. Thanks in advance for any
help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
Thanks for the response, but I checked the problem machine, and both of those
registry entries show an empty string.
While I love puzzles like this as much as the next guy, this is getting
REALLY ridiculous! ;)
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Claes Bergefall" wrote:
You should be able to change them in the registry at
HKEY_CURRENT_USER\Control Panel\International
or
HKEY_USERS\.DEFAULT\Control Panel\International
The value your looking for is sPositiveSign. It is set to an empty string on
my machine
/claes
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:73**********************************@microsof t.com...
I have good news and bad news.
The good news is that with Ignacio's suggestion we checked the
NumberFormatInfo parameters and found that for the problem machines the
PositiveSign Value is a 0, but only for en-US and only on the problem
machines.
I also verified that this is what was causing the problem by temporarily
changing my value to a 0 and got the errors.
The bad news is I cannot find any way to change the value back to a + sign
as it is on the non-problem machines and for all other culture settings.
I
also have no idea HOW the bad ones were set to 0 in the first place.
I found where you can change how the system treats negative numbers, but
nothing so far on setting the PositiveSign value. Has anyone seen this
before, or can anyone tell me how I might change the PositiveSign value?
Thanks for your responses earlier. It definitely helped us isolate the
problem.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
"Ignacio Machin ( .NET/ C# MVP )" wrote:
Hi,
You have some error in the format of the number, can you post the code in
question?
Also compare one working machine and one with the error regarding the
culture being used , especifucally the NumberFormatInfo benig used.
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"WhiteWizard" <Wh*********@discussions.microsoft.comwrote in message
news:9A**********************************@microsof t.com...
Have we got a STRANGE one going here.
We converted from 1.1 to 2.0 about 2 weeks ago and this has been a
problem
since then...but only on SOME machines in our development group. The
application runs fine using 1.1 and on 3 of the 8 machines in our
group.
It
is a Windows application.
Our appliation has many user controls, and panels/viewing areas that we
show
in our app. In our application we several areas where we have to take
a
string and parse it into other data types; for
instance--ushort.parse(strSysID). On the problem machines this
generates
the
following build error:
A first chance exception of type 'System.FormatException' occurred in
mscorlib.dll
TestPointSpec: Error TP 774 not a number 0 System.FormatException:
Input
string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ConfigurationFiles.TestPointSpecificationFile.Pars eEnumeration(UInt16
specID, String wholeEnum) in D:\C-5 RERP\PVCS
7-26-06\Common\ConfigurationFiles\TestPointSpecificatio nFile.cs:line
357
In other parts of the application, we may be using the string in a
different
way(ie. we use the string/convert it to an int and use it as an index),
and
it gets past the build process, but at run time generates the following
error, when trying to use a "0" in a string:
System.FormatException was unhandled
Message="Input string was not in a correct format."
Source="mscorlib"
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseUInt32(String value, NumberStyles options,
NumberFormatInfo numfmt)
at System.UInt16.Parse(String s, NumberStyles style,
NumberFormatInfo
info)
at System.UInt16.Parse(String s)
at
ApplicationFrame.SubsystemBrowserControl.GetSelect edRows(DataGrid
dg) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1290
at
ApplicationFrame.SubsystemBrowserControl.addTPmenu Item_Click(Object
sender,
EventArgs e) in D:\C-5 RERP\PVCS
7-26-06\PCIU_CSCI\UserInterfaceComponents\SubsystemBrow serControl.cs:line
1052
We know it has something to do with having a "0" in a string, but have
NO
idea, of why it happens on only some of the machines and not all
(luckily
I'm
not one of the problem machines), and also why it works with 1.1
version
of
the framework, and not 2.0.
Anyone have any ideas of what the problem is, or where we start
looking?
My apologies for the length of the post. Thanks in advance for any
help.
WhiteWizard
aka Gandalf
MCSD.NET, MCAD, MCT
did you ever solve this issue?
I am have the same problem. Can not insert a 0 (zero) into the datagridview.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Nobody |
last post by:
I have some code that I am trying to optimize for speed...
trying to squeeze every last CPU cycle out... I remembered an old trick
where dividing & multiplying can be sped up by using bitshifts...
|
by: Wescotte |
last post by:
Here is a small sample program I wrote in PHP to help illustrates
problem I'm having. The data base is using DB2 V5R3M0. The client is
WinXP machine using the iSeries Client Access Driver ver...
|
by: Gary Carson |
last post by:
Can anyone tell why the query below would throw a divide-by-zero
error? The only reason I can see for the error happening would be if
SUM() came out to be zero, but this never happens with the...
|
by: Chris |
last post by:
Hi,
a strange behaviour when working with exceptions :
when I divide and integer by 0 will an exception be thrown. OK
but, when I divide a double by 0 is no exception thrown ???
How come ?
...
|
by: Chris |
last post by:
Hi,
a strange behaviour when working with exceptions :
when I divide and integer by 0 will an exception be thrown. OK
but, when I divide a double by 0 is no exception thrown ???
How come ?
...
|
by: Kevin |
last post by:
Dim X as int32
Dim Y as int64
X = Y / 1024
gives me the error:
"Operator is not valid for type 'UInt64' and type 'Integer'."
I'm new to VB.NET and this is one of the reasons why I've...
|
by: Wescotte |
last post by:
<?php
global $TABLE_GL_DATA;
global $connect;
$PREPARED_SQL = odbc_prepare($connect, "INSERT INTO $TABLE_GL_DATA
VALUES (?,?,?,?,?,?,?)");
function Generate_GL_Data()
{
|
by: =?Utf-8?B?bWljaGFlbGd3ZWllcg==?= |
last post by:
Hello! I was working on some code the other day, and I came across an odd
discrepancy between the decimal and the double type.
If I attempt to divide a decimal by zero, the framework throws an...
|
by: david |
last post by:
I took old code and decided to modify it a bit, and I just noticed
that it does not compile at all and before server one of severs (main)
crashed in the system it was working fine (I am really sure...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |
