Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Behavior change to TRANSFORM() in VFP7
Message
 
To
07/10/2004 04:18:38
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00949444
Message ID:
00949454
Views:
26
Tore,
I think there is an error in that function:
? NTOC(0.2, 1) &&-> 0.2
? NTOC(0.2, 0) &&-> 0
* but
? NTOC(0.6, 1) &&-> 0.6
? NTOC(0.6, 1) &&-> 1
>Hi Neil,
>
>I don't know of any behavior change, but if there is, it's probably documented. Why not use transform(0.20,'99999999.9')? Here is a generic function I wrote some years ago:
>FUNCTION NTOC && Numeric to character, trims the result, optional number of decimals)
>   PARAMETERS lnInData,lnDecimal
>   IF PCOUNT()=1
>      lnDecimal=0
>   ENDIF
>RETURN LTRIM(STR(lnInData,10,lnDecimal))
>ntoc(0.20,1)=0.2
>ntoc(0.20)=0
>
>>I have noticed a behavior change in the TRANSFORM() function in VFP7.
>>
>>In VFP6,
>>
>>? TRANSFORM(0.20)
>>0.2
>>
>>But in VFP7 (I'm running SP1)
>>
>>? TRANSFORM(0.20)
>>0.20
>>
>>This is causing me quite a problem, does anyone know why I'm getting this result and how to rectify it? Is this behavior also in VFP8? The help file still states that trailing zeros after a decimal point should be truncated.
>>
>>Neil Shumsky
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform