Whenever I right an SP I use..
CREATE PROCEDURE someSP
@somthing AS int,
@somethingelse AS varchar(50)
I don't know if not using the AS is ok or not but give it a go, see if it
fixes it
Ade
-Original Message-
From: S. Isaac Dealey [mailto:[EMAIL
**
WESTMINSTER CITY COUNCIL
Please refer to the disclaimer beneath this message
**
YOu can comment out the call to the stored procedure and then output all the
having the
problem was using CFMX and M$SQL. Hope this helps you out and that I didnt
misunderstand that whole think last week.
Josh
-Original Message-
From: Adams, Stephen [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 7:31 AM
To: CF-Talk
Subject: RE: more cfstoredproc issues
Thanks for the suggestion josh. I didn't think I had used any cf_sql_date
flags... I did a search and replace on wwwroot including subfolders just to
be sure and it didn't replace anything, so...
I do not know if this may be the underlying cause of the
error but I do know
that if sql is your
Figured it was a long shot, but I tried it -- no dice. Thanks for the
suggestion Ade,
Whenever I right an SP I use..
CREATE PROCEDURE someSP
somthing AS int,
somethingelse AS varchar(50)
I don't know if not using the AS is ok or not but give it
a go, see if it fixes it
Dude... In your cfprocparam tag, you write this:
cfprocparam type=in dbvarname=LibraryID
You should write:
cfprocparam type=in dbvarname=@LibraryID
AFAIK, you need the @ symobol. Also, the word AS is unnecessary... You
don't need it for any variable declaration in a stored proc.
Dude... In your cfprocparam tag, you write this:
cfprocparam type=in dbvarname=LibraryID
You should write:
cfprocparam type=in dbvarname=@LibraryID
AFAIK, you need the @ symobol.
hmmm... I'll try it, but I've got dozens if not hundreds of stored procedure
calls in this app, and none of
version...
-Original Message-
From: S.Isaac Dealey [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 9:36 AM
To: CF-Talk
Subject: RE: more cfstoredproc issues ...
Dude... In your cfprocparam tag, you write this: cfprocparam
type=in dbvarname=LibraryID
You should write
the wrong var name just switches to the first
version...
-Original Message-
From: S.Isaac Dealey [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 9:36 AM
To: CF-Talk
Subject: RE: more cfstoredproc issues ...
Dude... In your cfprocparam tag, you write this:
cfprocparam
Never underestimate the power of context highlighting!
Which in this case didn't catch the fact that a CFML comment ( !--- ) in
the middle of my stored procedure was terminated with an HTML comment... (
-- ) ... sigh... which was the source of the problem... How did I figure
this out? I ran this
didn't help huh...
-Original Message-
From: S.Isaac Dealey [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 11:13 AM
To: CF-Talk
Subject: RE: more cfstoredproc issues ...
Actually the names in the dbvarname attribute are completely ignored by the
cf-server as far as I
: S.Isaac Dealey [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 11:13 AM
To: CF-Talk
Subject: RE: more cfstoredproc issues ...
Actually the names in the dbvarname attribute are completely ignored by
the
cf-server as far as I or anyone else has been able to determine. They have
automatically
converts the Char into a date object - as long as the format is correct.
-mk
-Original Message-
From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 8:52 PM
To: CF-Talk
Subject: Re: more cfstoredproc issues -- ARGH!!
The other thing that really
S. Isaac Dealey wrote:
Yea, it turned out to be the cf_sql_date that was causing the wrong number
of parameters error message... so changing that to cf_sql_timestamp solved
the problem... Better support for cfstoredproc ( naming and better error
handling in particular. ) would be _great_ to
S. Isaac Dealey wrote:
Yea, it turned out to be the cf_sql_date that was causing
the wrong number
of parameters error message... so changing that to
cf_sql_timestamp solved
the problem... Better support for cfstoredproc ( naming
and better error
handling in particular. ) would be _great_
15 matches
Mail list logo