This is exactly the type of problem that I have been having & there seemed to be no reason for the failures. The calculations are very unstable. I try to get around this by using 2 fudge factors - 1 that I use to enforce floating point but which perturbs the accuracy. I compensate by a second fudge factor that catches values in a very narrow interval. After hours of testing it was the only consistent method that I could find. I can increase the accuracy indefinitely but at the cost of 2 characters per decimal place.
I think all of the above mentioned functions are wonky & totally unreliable with floating point. They are not even predictable.
Patrick,
You might be right Patrick but I get the sense the problem is deeper & more serious than that. For instances, there are about 5 functions for effectively executing a constructed string. If you feed them exactly the same string they give different results on occasions.
Howard,
Add 0.000001 to all your numbers & then check for a narrow range say + or - 0.0001 about 24. I bet it will work. Absolutely everything must be floating point though. Even the 24 must be written as 24.0.
This is kind of like practicing voodoo in my opinion but it does give consistent results.
Jens,
I think your challange may have pushed kixtart beyond its capabilities.
[ 17. September 2002, 00:21: Message edited by: Jack Lothian ]
