Received: from keiko.petstore.com (IDENT:root@mail.petstore.com [208.25.91.9])
	by hub.org (8.9.3/8.9.3) with ESMTP id RAA26742
	for <pgsql-interfaces@hub.org>; Thu, 1 Jul 1999 17:47:42 -0400 (EDT)
	(envelope-from asif@petstore.com)
Received: from petstore.com (dhcp105.petstore.com [10.0.0.105])
	by keiko.petstore.com (8.8.7/8.8.7) with ESMTP id OAA08750;
	Thu, 1 Jul 1999 14:52:21 -0700
Message-ID: <377BE2EF.4A5EA349@petstore.com>
Date: Thu, 01 Jul 1999 14:51:43 -0700
From: "S. Asif Hassan" <asif@petstore.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
CC: "'pgsql-interfaces@hub.org'" <pgsql-interfaces@hub.org>
Subject: Re: 
References: <01BEC3D4.AD2F64C0.jt-kirkpatrick@mpsllc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I ended up changing the data types to float8...
Why the warning against using float4?
Will I encounter problems using float8?

-asif.

JT Kirkpatrick wrote:

> >Subject: bug: Access sees money types incorrectly
>
> it's the odbc -- it doesn't recognize the money type.  i have had to use
> int4, storing all entries *100 (i.e. 35.99 as 3599), and then on reports be
> sure to divide by 100.  DON'T use float4!!  in postgres6.5 i understand the
> newer numeric type is available, but i don't know if the odbc can use it
> yet. . .
>
> jt