Re: DBLOAD changes numbers!

Uhmm, Switch your data types to decimal. The calculations will be slower, but you don't have to worry about the floating point precision issue. You will find this numeric inprecision in all your applications. (I forget the correct term for floating point errors.) That's why you have doubles and longer word lengths. The longer the word the better the precision. -HTH Mikey Mjgator wrote: > > Am loading rows into OWS on NT. Have a field defined as float. Load in > delimited rows with a number such as .03. It loads as .02999999999. Why in > the WORLD would it do this? Makes my calculations come out absurd and my > tables in screens have to be much wider. I really only need precision of 3 or > so. Thoughts? -- #include <std_disclaimer.h> /* Mike Segel (MS385) */ #include <No_Spam.h> #ifdef OFFENDED_BY_CONTENT The author takes no responsibility for this post. Any resemblence to a coherent rational thought is purely coincidence. -The Management. #endif ***************************** * Attention * -*- Due to AGIS's Refusal to Act Responsibly -*- Due to ACSI's Refusal to Act Responsibly We are blocking all of their domains at the packet level. This block will exist until they modify their policies to conform to existing RFCs and net community standards. We encourage all ISPs and domain holders to do the same. *****************************