The division operator returns an INT according to the T-SQL reference. It also says that the division operator drops the remainder. The data comes from a NUMERIC field and I'm storing the value into a VARCHAR(10) field so that's not the problem, it just drops the remainder by default.
I tried one using: newcolumn = '' +mycolumn/2+ '.' +mycolumn%2+ '' This gave me an error that VARCHAR data "." cannot be converted to INT, however the field that it's being inserted into is a VARCHAR(10) field. I'll try some of the CAST() CONVERT() options, thanks. Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net [EMAIL PROTECTED] (704) 569-0801 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to [EMAIL PROTECTED] ************************************************************************ ************* -----Original Message----- From: Craig Dudley [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 11:21 AM To: CF-Talk Subject: RE: T-SQL division drops the decimal? Silly question, but what datatype is the column which holds your result? Not forgotten about it and left it as an int have you? Even if not, I'd play with the datatypes a bit, it may be your issue. -----Original Message----- From: Joshua Miller [mailto:[EMAIL PROTECTED] Sent: 31 July 2003 16:15 To: CF-Talk Subject: T-SQL division drops the decimal? How do others on the list deal with this? I have a query that takes a value from the database and divides by 2 and inserts that value into another table, however SQL Server (T-SQL) drops the decimal place, so 1/2 of 1 is 0 according to T-SQL. Any idea how to overcome this? That seems really odd .... if I WANTED to round I could use FLOOR() or CEILING() to round, why make it the default in T-SQL ???? Thanks, Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net <http://www.garrisonenterprises.net/> [EMAIL PROTECTED] (704) 569-0801 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] ************************************************************************ ************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
