yes, I could do it that way. However, all dates I try to insert are giving the
error, not just ones I'm using the function #now()# in.
Turns out the issue is my data source in CF. We have been using the ODBC socket
to connect CF to the System DSN which uses the SQL Native driver. When I
Turns out what is causing the error is the line
EditDate=cfqueryparam value=#now()# cfsqltype=cf_sql_timestamp
the EditDate is a datetime field.
Any ideas?
thanks!
~|
Order the Adobe Coldfusion Anthology now!
database have built in functions for getting the current date, so you don't
need to use CF.
e.g. for sql server use
editdate - getDate()
On Fri, May 6, 2011 at 9:21 PM, Nicki Tabb vnt...@alaska.edu wrote:
Turns out what is causing the error is the line
EditDate=cfqueryparam
I have tested the query using 0 instead of No for the default form value (see
reply thread) and I am still receiving the Invalid Precision Value error.
In the error, it highlights the last line as the issue (although sometimes that
is deceiving)
cfqueryparam cfsqltype=cf_sql_varchar value
The default is NO so it always has a value
What is the value of #FORM.LoanerYN# when you try to insert it in the
bit field?
~|
Order the Adobe Coldfusion Anthology now!
Surely a bit field will need 0 or 1, not a string? Or was that not what you
meant?
- Original Message
From: Nicki Tabb vnt...@alaska.edu
To: cf-talk cf-talk@houseoffusion.com
Sent: Fri, 18 February, 2011 15:32:19
Subject: Re: Invalid Precision Value from SQL Server CF9
The default
SQL will read a NO or FALSE or 0 as the same
Surely a bit field will need 0 or 1, not a string? Or was that not what you
meant?
The default is NO so it always has a value
What is the value of #FORM.LoanerYN# when you try to insert it in the
bit field?
...@alaska.edu]
Sent: Friday, February 18, 2011 1:17 PM
To: cf-talk
Subject: Re: Invalid Precision Value from SQL Server CF9
SQL will read a NO or FALSE or 0 as the same
~|
Order the Adobe Coldfusion Anthology now!
http
sorry,
I guess I meant that, when using CF, I have never had issues with No or False
or 0 being read as the same by the SQL Server
No it doesn't.
Here is an example on SQL 2005:
declare @test table (
testVal bit
)
insert into @test (testval) values (0);
insert into @test (testval)
CF will read in bit values from SQL Server and evaluate them as
equivalent to true/false or yes/no. However, SQL Server expects 0 or 1
from ColdFusion when writing to a bit field. There's probably a UDF on
CFLib.org that converts CF boolean values into strict bit values, but
here's one I
I am testing some code on CF9 before we move all our sites from CF8 and have
come upon this issue. The page that runs the query below is returning an
Invalid Precision Value error.
cfquery name=addVRRF datasource=eworfs
INSERT INTO VRRFs (RequestDateTime, Name, Email, Phone, Department, ENum
is returning an
Invalid Precision Value error.
cfqueryparam cfsqltype=cf_sql_bit value=#FORM.LoanerYN#,
I am using SQL Server 2008 (driver is SQL Native client 10.0). This query
works fine on CF8 with the same database but gives the error on the CF9
installation. From what i can find through
have you looked at the docs to see how dateFormat() is used?
it's quite clear you haven't... take 5 secs and it will be VERY
evident amigo
tw
Sent from my iPhone... don't hate
On Oct 27, 2009, at 12:10 AM, Matthew Smith chedders...@gmail.com
wrote:
wrap dateformat() around the
Getting this on a query.
Define Getting. Where are these values displayed?
~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
wrap dateformat() around the dateadd() function.
NO. createOdbcDate expects a date value as a parameter.
One should never submit a formated date to this function,
the date will be de-formated anyway, with the risk that the format is
not compatible
(ie: european date format).
Right, my understanding is that cfqueryparam will take care of making sure
the db gets the date as it expects it. If I'm not wrong, you should just
ditch the CreateObdcDateTime call.
Dominic
2009/10/27 Claude Schneegans schneeg...@internetique.com
wrap dateformat() around the dateadd()
Getting this on a query.
Parameters:
nextthursday = {ts '2009-10-29 00:00:00'}
lastthursday = 2009-10-22 00:00:00.000
cffunction access=public name=qry_contestthisweek_get output=false
returntype=query
cfargument name=lastthursday type=string default=
cfset nextthursday =
wrap dateformat() around the dateadd() function.
tw
Sent from my iPhone... don't hate
On Oct 27, 2009, at 12:02 AM, Matthew Smith chedders...@gmail.com
wrote:
Getting this on a query.
Parameters:
nextthursday = {ts '2009-10-29 00:00:00'}
lastthursday = 2009-10-22 00:00:00.000
wrap dateformat() around the dateadd() function.
tw
Sent from my iPhone... don't hate
On Oct 27, 2009, at 12:02 AM, Matthew Smith chedders...@gmail.com
wrote:
Still the same:
cffunction access=public name=qry_contestthisweek_get output=false
returntype=query
cfargument
I am receiving the following CF error:
I don't have an answer for the question you asked, but I think you're asking
the wrong question.
First, instead of having a column which contains a comma-delimited list,
you'd probably be better off with a lookup table with those values instead,
and an
I am receiving the following CF error:
Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft
Access Driver]Invalid precision value
If I try to run the query directly from MS Access, using the same SQL, I
receive no error and the results
Rogan [mailto:[EMAIL PROTECTED]
Sent: Friday, May 27, 2005 8:41 AM
To: CF-Talk
Subject: Invalid precision value
I am receiving the following CF error:
Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft
Access Driver]Invalid precision value
I am receiving the following CF error:
Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC
Socket][Microsoft][ODBC Microsoft Access Driver]Invalid
precision value
If I try to run the query directly from MS Access, using the
same SQL, I receive no error
I am getting an occasional error message upon form submission that says:
Invalid Precision Value
Predictably enough, the line referenced is my database insert line,
which reads as follows:
cfinsert datasource=Falls tablename=tblFalls
Noteworthy is the fact that there are close to 50 form
, Timothy
[EMAIL PROTECTED] wrote:
I am getting an occasional error message upon form submission that says:
Invalid Precision Value
Predictably enough, the line referenced is my database insert line,
which reads as follows:
cfinsert datasource=Falls tablename=tblFalls
Noteworthy is the fact
For all those who helped with the Invalid Precision value error that came
up when inserting from a CSV, thanks - I figured it out on my own finally -
it turns out that for whatever reason, I had to go into Excel and highlight
that column and manually set the cells to TEXT, then resave it, even
I'm uploading a csv file into Access in a loop using the
CSV2Data custom tag- adding new records and I get the following error:
ODBC Error Code = S1104 (Invalid precision value)
I've uploaded ten csv files that all worked well but this one blows up...
What can cause this error message
this bombs out the insert/update.
Andy
-Original Message-
From: Rafael Alan Bleiweiss [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 12:47 PM
To: CF-Talk
Subject: invalid precision value
I'm uploading a csv file into Access in a loop using the
CSV2Data custom tag- adding new
OK Field 1, 2, 3 - This is, perhaps reasonable so, OK, 4-This tends to
Blow Up, many times.
Field 4 tends to end up as 2 or more fields, and if your tag doesn't fix
this bombs out the insert/update.
Further research shows that previous csv uploads had commas in that field
and they were
29 matches
Mail list logo
