RE: SP pulling my hair out!!!

2002-04-16 Thread Tony_Petruzzi
hasn't anyone heard of ALTER PROCEDURE ;) Anthony Petruzzi Webmaster 954-321-4703 [EMAIL PROTECTED] http://www.sheriff.org -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:33 PM To: CF-Talk Subject: Re: SP pulling my hair out!!! cfstoredproc

Re: SP pulling my hair out!!!

2002-04-16 Thread Neil H.
:04 PM Subject: RE: SP pulling my hair out!!! Neil, I usually use #createodbcdatetime(var)# or #createodbcdate(var)# to correctly format the date string. Mark -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 9:50 PM To: CF-Talk Subject: Re

RE: SP pulling my hair out!!!

2002-04-16 Thread Mark A. Kruger - CFG
you've identified it as a date. I've always thought that was a bit of an oversite. mark -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 9:54 AM To: CF-Talk Subject: Re: SP pulling my hair out!!! I have found this to be the problem. So a data

Re: SP pulling my hair out!!!

2002-04-16 Thread Neil H.
: RE: SP pulling my hair out!!! Excellent. I'm glad it's working for you. Yes it is strange. From the command line (query analyzer) you can put '5/26/2002' and SQL will automatically parse it. But the ODBC driver cannot differentiate that syntax from string syntax - it doesn't automatically

Re: SP pulling my hair out!!!

2002-04-16 Thread Neil H.
Anyone have any code samples of CFSTOREDPROC and date usage. I just can't get it to work! Neil - Original Message - From: Neil H. [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Tuesday, April 16, 2002 2:19 PM Subject: Re: SP pulling my hair out!!! I receive this error when I

Re: SP pulling my hair out!!!

2002-04-16 Thread Chris Terrebonne
, SQL will accept a char/varchar as a datetime value. HTH, Chris -- Original Message From: Neil H.[EMAIL PROTECTED] Subject: Re: SP pulling my hair out!!! Date: Tue, 16 Apr 2002 15:05:01 -0400 Anyone have any code samples of CFSTOREDPROC and date usage. I

Re: SP pulling my hair out!!!

2002-04-16 Thread Neil H.
] Sent: Tuesday, April 16, 2002 3:14 PM Subject: Re: SP pulling my hair out!!! Not sure if this has been addressed yet but you should be able to send the date as a CHAR and have SQL determine if its a date: cfprocparam type=In cfsqltype=CF_SQL_CHAR variable=DateValue value=#DateFormat(Now

Re: SP pulling my hair out!!!

2002-04-16 Thread Chris Terrebonne
Glad that helped! SQL is really picky about what you can call a Date but if you call it a Char, SQL is usually pretty good at figuring it out. Chris -- Original Message From: Neil H.[EMAIL PROTECTED] Subject: Re: SP pulling my hair out!!! Date: Tue, 16

SP pulling my hair out!!!

2002-04-15 Thread Neil H.
I only have a little hair left so PLEASE throw ideas at me! I get this error: Microsoft][ODBC SQL Server Driver]COUNT field incorrect or syntax error Hint: The cause of this error is usually that your query contains a reference to a field which does not exist. You should verify that the fields

RE: SP pulling my hair out!!!

2002-04-15 Thread Mark A. Kruger - CFG
Neil, better post your code - hard to deal with this error without looking at it. Mark -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 8:46 PM To: CF-Talk Subject: SP pulling my hair out!!! I only have a little hair left so PLEASE throw ideas

Re: SP pulling my hair out!!!

2002-04-15 Thread Neil H.
to protect the innocent Neil - Original Message - From: Mark A. Kruger - CFG [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Monday, April 15, 2002 10:02 PM Subject: RE: SP pulling my hair out!!! Neil, better post your code - hard to deal with this error without looking

Re: SP pulling my hair out!!!

2002-04-15 Thread Neil H.
Subject: Re: SP pulling my hair out!!! cfstoredproc datasource=#DSN# procedure=sp_MYSP cfprocparam type=In cfsqltype=CF_SQL_INTEGER variable=1 value=#1# cfprocparam type=In cfsqltype=CF_SQL_MONEY variable=2 value=#2# cfprocparam type=In cfsqltype=CF_SQL_DATE

RE: SP pulling my hair out!!!

2002-04-15 Thread Mark A. Kruger - CFG
Neil, I usually use #createodbcdatetime(var)# or #createodbcdate(var)# to correctly format the date string. Mark -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 9:50 PM To: CF-Talk Subject: Re: SP pulling my hair out!!! cfprocparam type

RE: SP pulling my hair out!!!

2002-04-15 Thread Mark A. Kruger - CFG
Neil, Ok - I will assume that none of your variables are actually numbers (cause that would cause an error as well). I use the Dbvarname on IN variables as well as out variables as in: cfprocparam type=In cfsqltype=CF_SQL_INTEGER dbvarname=Sendall value=1 cfprocparam type=Out

RE: SP pulling my hair out!!!

2002-04-15 Thread Dave Watts
cfprocparam type=In cfsqltype=CF_SQL_DATE variable=3 value=#3# 3 datetime, This is the culprit. What is the normal way to handle this?! That's not a valid CF variable name. In CF, variable names can consist of letters, numbers and underscores, but the first character can't

RE: SP pulling my hair out!!!

2002-04-15 Thread Ken Wilson
Try changing it to: cfsqltype=CF_SQL_TIMESTAMP -Original Message- From: Neil H. [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:50 PM To: CF-Talk Subject: Re: SP pulling my hair out!!! cfprocparam type=In cfsqltype=CF_SQL_DATE variable=3 value=#3# @3

RE: SP pulling my hair out!!!

2002-04-15 Thread Mark A. Kruger - CFG
- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 10:06 PM To: CF-Talk Subject: RE: SP pulling my hair out!!! cfprocparam type=In cfsqltype=CF_SQL_DATE variable=3 value=#3# @3 datetime, This is the culprit. What is the normal way to handle this?! That's not a valid CF