D
Dan C Douglas
I have just installed VS.NET 2003 on my computer. I have a project that I have been developing on VS.NET 2002. I haven't upgraded this project to VS.NET 2003 yet and I am still developing it in VS.NET 2002.
When I am putting values from my SQLDataReader into labels and text boxes I am getting results such as 400.0000, or 25.90.
For example...
? dr("CostsPerBin")
returns
400D {Decimal}
[Decimal]: 400D
returns
"400.0000"
It used to return "400" before I installed VS.NET2K3
Obviously it is returning 4 decimals because it is the scale of the data type in SQL. This is a money field, although other fields that are decimal with a scale of 2 return results such as 90.40 when converted to a string.
Any ideas?
It works normally on our dev box and production server and also on other developers machines.
I am the only one in the office who has install VS.NET2K3, but I don't understand how it would change these results.
Is this a feature of .NET Framework 1.1 ? (project is still .NET framework 1.0 as I didn't upgrade it though)
Thanks,
Dan
When I am putting values from my SQLDataReader into labels and text boxes I am getting results such as 400.0000, or 25.90.
For example...
? dr("CostsPerBin")
returns
400D {Decimal}
[Decimal]: 400D
? dr("CostsPerBin").toString
returns
"400.0000"
It used to return "400" before I installed VS.NET2K3
Obviously it is returning 4 decimals because it is the scale of the data type in SQL. This is a money field, although other fields that are decimal with a scale of 2 return results such as 90.40 when converted to a string.
Any ideas?
It works normally on our dev box and production server and also on other developers machines.
I am the only one in the office who has install VS.NET2K3, but I don't understand how it would change these results.
Is this a feature of .NET Framework 1.1 ? (project is still .NET framework 1.0 as I didn't upgrade it though)
Thanks,
Dan