Re: Float Percision with MS Access 97

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
float4.
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
http://phonecard.yahoo.com/