The real problem here (IMHO!) is NOT whether or not it is a bug or that the vfp7 documentation does NOT match the way the function behaves, but that the function was changed between version 6 and 7. The documentation matched the function in version 6 and many developers used the function expecting it to behave that way with success. Now, when building the same app in vfp7, those functions will return different results and that requires a lot of changing code to get the result you need! There was no warning when upgrading to vfp7 to be aware of this, or did I miss it????
Tracy
>It returns "10", like the docs...
>
>>What does VFP 6 return on that?
>
>>
>>>Try to explaind following
? Transform(10.00)
>>>
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
