Leon945
03-06-2009, 10:36 AM
Hi,
I have a small yet big issue..
To make the story short, apparently 2 times out of 4000 the Convert.toDouble instruction ignores the "." in a number,
example
Convert.toDouble("58.15") will return 5815 which is completely not correct and is of major importance due to the fact that this value represents an amount which will be charged to a costumer.
Fortunately, the costumer was only charged the "58.15" because the parameter was passed as string.
The information stored in my DB was stored using the toDouble.
I have displayed the string value before and after the Convert.toDouble and it is the correct value.
Is there a known bug for this? Or should i be taking something else into account?
Strange thing is, it happened in 2 out of 4000 operations.
I have a small yet big issue..
To make the story short, apparently 2 times out of 4000 the Convert.toDouble instruction ignores the "." in a number,
example
Convert.toDouble("58.15") will return 5815 which is completely not correct and is of major importance due to the fact that this value represents an amount which will be charged to a costumer.
Fortunately, the costumer was only charged the "58.15" because the parameter was passed as string.
The information stored in my DB was stored using the toDouble.
I have displayed the string value before and after the Convert.toDouble and it is the correct value.
Is there a known bug for this? Or should i be taking something else into account?
Strange thing is, it happened in 2 out of 4000 operations.