>I understand. Thanks for all your input. I tried to get the division to work on the code you had sent me but after some tweaking of it I still couldn't figure out how to do it. If you have an updated class I would be very interested in seeing it. Is it able to return more than 15 significant digits?
>
>Thanks again for your help.
The .Divide() method was
very incomplete. In the current version (on my computer) I get the correct digits, but still have to figure out where to put the decimal point.
And yes, the division is supposed to work with any desired precision - the only limit that applies is the size of VFP arrays, used internally for calculations (basically, one array element per digit).
BTW, I would be interested in information from you, about why anybody would need precision higher than 15 significant digits, to include it in the comments.
In the current implementation, I don't specify a number of significant digits, instead, a fixed number of decimals - which can be as high as you desire. For instance, 50 or 100 decimals would be no problem.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
