This is probably happening because of the way the numeric is defined. By first casting your numeric value as real, and then to varchar, you should be able to circumvent this problem.
Run this in QA to better understand what I am talking about.
Code:
Declare @N1 NUmeric(10,2)
Declare @N2 Numeric(10,1)
Set @N1 = 5.8
Set @N2 = 5.8
Select Cast(@N1 As Char(9)),
Cast(@N2 As Char(9)),
Cast(Cast(@N1 As Real) As VarChar(9))
Hope it helps.
-George
Strong and bitter words indicate a weak cause. - Fortune cookie wisdom
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.