I am sorry, but I guess I did not make my question
clear. I am not looking for greater backend precision
(ie moving to float8). There seems to be a
mis-comunication between Access and postgres with
Access is seeing the number with fewer digits than
want must be in postgres. If I do a :
UPDATE Parts SET Count = round(Count,4);
Then the access query from my first email will work.
This is a pain right now because my users will get a
write conflict error, call me, I will find the
offending field, do and Update with the round(x,4),
then it will work.
I could fix it by putting round(x,4) with all float
fields, but this seems like a poor fix.
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
In response to
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2001-08-20 23:24:55|
|Subject: Re: New CVS doesn't compile|
|Previous:||From: Tom Lane||Date: 2001-08-20 20:54:05|
|Subject: Re: Float Percision with MS Access 97 |