S
Scott
I'm using the GetSchemaTable method of SqlDataReader to determine the
precision / scale of decimal columns returned from a SQL Server stored
procedure. If a column coming back is defined as decimal, NumericPrecision
and NumericScale work as expected. However, if the column is defined as
money, NumericPrecision returns a value of 19, and NumericScale returns 255.
I expected NumericScale to be 4 for money values (which would match the
number of decimal places that SQL Server uses for that data type).
Can anyone explain why NumericScale is 255 for money types instead of 4? Is
this a bug or a feature? Is there anything I can do to make NumericScale
represent the correct number of digits for money values?
Thanks in advance for your help!
Scott
precision / scale of decimal columns returned from a SQL Server stored
procedure. If a column coming back is defined as decimal, NumericPrecision
and NumericScale work as expected. However, if the column is defined as
money, NumericPrecision returns a value of 19, and NumericScale returns 255.
I expected NumericScale to be 4 for money values (which would match the
number of decimal places that SQL Server uses for that data type).
Can anyone explain why NumericScale is 255 for money types instead of 4? Is
this a bug or a feature? Is there anything I can do to make NumericScale
represent the correct number of digits for money values?
Thanks in advance for your help!
Scott