I would post the whole query... sometimes the line number is not precisely
correct :)
-mk
Mark A. Kruger, MCSE, CFG
(402) 408-3733 ext 105
www.cfwebtools.com
www.coldfusionmuse.com
www.necfug.com
-Original Message-
From: Matthew Smith [mailto:chedders...@gmail.com]
Sent: Wednesday,
On 2/18/10, Matthew Smith wrote:
I am getting an error in a query that does not happen with crystaltech.
Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC SQL Server
Driver]Invalid precision value
I am betting that a reputable hoster such as
That did it.
Set up a regular sql server datasource and it worked.
Thank you so much.
Just out of curiosity, when should I use nvarchar as opposed to varchar?
On Thu, Feb 18, 2010 at 12:20 PM, Jochem van Dieten joch...@gmail.comwrote:
On 2/18/10, Matthew Smith wrote:
I am getting an
Just out of curiosity, when should I use nvarchar as opposed to varchar?
nvarchar allows for an expanded set of characters, for example if you want
your app to be able to handle double byte characters for non latin languages
such as Chinese or Russian you would use nvarchar or ntext.
However,
I also believe (though I'm happy to be corrected if I'm wrong) that
you can later safely switch from a varchar to an nvarchar. You'd be in
danger of truncating data if you went from nvarchar to varchar, but
since varchar is a subset of nvarchar, changing the data type at a
later date should be
5 matches
Mail list logo
