Thanks Helen and all the other who answered.

[]s

Carlos
WarmBoot Informatica - http://www.warmboot.com.br
FireBase - http://www.FireBase.com.br

HB> At 11:15 AM 24/01/2003 -0300, you wrote:

>>MT> I guess that depends a little on what you want. Are the FLOAT fields in
>>MT> Paradox _real_ floats?
>>
>>That's my doubt too. I do not know how paradox (or even the BDE)
>>handle this. I would like to use the firebird datatype that has the
>>most similar "handling" as Paradox-Float to avoid customers complaints
>>about diferent results after the transition from Pdox to FB.

HB> Carlos,
HB> Paradox floats are single-precision and suffer from the same problems as IB
HB> floats. If you don't see any evidence in the code that any rounding rules
HB> have been applied to the values to correct for precision errors, I suppose
HB> you can assume that your customer doesn't care about them.

HB> If *you* care about them, you will probably apply the types that will
HB> achieve the precision you need and will explain to your customer that this
HB> is one more advantage of moving over to Firebird...that their calculation
HB> results will possibly be different (and more accurate).

HB> I like Ann's rule of thumb: use numeric() for things you count, double for
HB> things you measure. Just make sure your numerics have enough scale and
HB> precision to accommodate the results of calculations.

HB> heLen





HB> To unsubscribe from this group, send an email to:
HB> ib-support-unsubscribe@egroups.com



HB> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/