Received: from osage.gate.net (root@osage.gate.net [198.206.134.25])
	by hub.org (8.9.1/8.9.1) with ESMTP id RAA25161
	for <pgsql-interfaces@hub.org>; Thu, 7 Jan 1999 17:02:40 -0500 (EST)
	(envelope-from bill@hammondgroves.com)
Received: from Bill..hutto.com (tsver1-202.gate.net [199.227.29.202]) by
	osage.gate.net (8.8.6/8.6.12) with SMTP id RAA76380;
	Thu, 7 Jan 1999 17:02:21 -0500
Message-Id: <199901072202.RAA76380@osage.gate.net>
From: "Bill Hutto" <bill@hammondgroves.com>
Organization: Hammond Groves
To: pgsql-interfaces@hub.org
Date: Thu, 7 Jan 1999 17:01:42 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [INTERFACES] Re: pgsql-interfaces-digest V1 #180
Reply-to: bill@hammondgroves.com
CC: Byron Nikolaidis <byronn@insightdist.com>,
	"Thomas G. Lockhart" <lockhart@alumni.caltech.edu>,
	"Ken J. Wright" <ken@ori-ind.com>
Priority: normal
In-reply-to: <3694E896.FE9B547A@insightdist.com>

> Its not exactly clear what you are trying to do.  But I'll take a guess at it.
> In the postgres database, the "amount" field is obviously of type money.  The
> sql statement, which I haven't seen, is probably trying to do an expression on
> that column.  Unfortunately, you can't easily do expressions on a money field in
> Postgres, without casting it or something like that.  And since the Jet is just
> sending the statement, it isn't going to work.  (I know you mentioned quotes,
> but the error message above suggests this has nothing to do with quotes -- it is
> some expression that is killing it.  And besides, if it were a quote thing, the
> error message would have been different.)

I'm assuming the error was caused by the Jet passing a float on 
the update. It probably has something to do with DAO. I tested 
ODBCDirect using a SQL Insert and was able to pull it off (with the 
quotes).

> 
> I recommend forgetting about the money type, and just stick with float for now.
> When we have full Numeric() support, then you can use a SQL_NUMERIC or
> SQL_DECIMAL to get the right precision.  You will not be able to use dollar
> signs and commas, but I don't think that is a show stopper, is it?

<snip>

I was just asking if the Money type could be converted to the 
appropriate type (SQL_NUMERIC according to my docs) so that I could 
bind the column to a control, as well as just generally use DAO to 
manipulate the data, thereby making it easier to use any DBMS with 
little mods. If I have to wait for the Numeric type implementation, I 
can probably handle that :).

Thanks,
Bill