Well... I use the money datatype in SQL server for our prices. I have had
not issues.
When we output, we use #dollarformat(queryname.price)#. Works for what we
do.
-Original Message-
From: Charlie Griefer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 9:23 AM
To: CF-Talk
hmm... this was the page i saw that seemed to strongly suggest that
the money datatype could be problematic in terms of accuracy (even
provided sample SQL to run in query analyzer to see the results):
http://tinyurl.com/6fh8hl
On Tue, Jun 10, 2008 at 9:55 AM, Jacob [EMAIL PROTECTED] wrote:
Charlie Griefer wrote:
Is there any bottom line recommendation on using the Money datatype
in SQL Server? I've googled and found a lot of folks say not to use
it because of accuracy issues (and of course, the fact that it's
proprietary), but I haven't seen any that suggest a better
On Tue, Jun 10, 2008 at 10:34 AM, Jochem van Dieten
[EMAIL PROTECTED] wrote:
Charlie Griefer wrote:
Is there any bottom line recommendation on using the Money datatype
in SQL Server? I've googled and found a lot of folks say not to use
it because of accuracy issues (and of course, the fact
Make sure you read this message as UTF-8 (the list still strips the
charset from the content-type header).
Charlie Griefer wrote:
There are some people here who suggest that it makes the database more
self documenting, and I don't disagree with that... but if there are
indeed accuracy
Retry, and hopefully the charset stuff now works.
Make sure you read this message as UTF-8 (the list still strips the
charset from the content-type header).
Charlie Griefer wrote:
There are some people here who suggest that it makes the database more
self documenting, and I don't disagree
6 matches
Mail list logo
