Re: Passing Parms to Query

[jpcarr@xxxxxxxxxxxx]

Paul

Thanks,  you hit the nail on the head.   I got it to work before reading
your post.   I am passing a CLP variable to the command and the contents of
the variable had to have the quotes  "Just Right"  .    The numeric values
worked ok.  It was a classic quoting problem.

Thanks everyone for your help.

John Carr







> I'm using a CLP variable as the SETVAR and I get an error saying  "
'xxxxx'
> is not a column in the table"   Where xxxx is the value in my CLP
variable.

Sounds like a classic quoting problem.

Suppose the column you are matching is called NAME, and you are trying to
match the value 'Carr'.  The SQL statement would be ...WHERE NAME='Carr'.
If the single quotes are omitted, or replaced with double quotes, you end
up
with ...WHERE NAME=Carr or ...WHERE NAME="Carr".  Both of these have the
same meaning: where the value of the NAME column matches the value of the
Carr column.

If this looks like a match for your problem, try simply wrapping your
variable in single quotes before you pass it in.

--
Paul




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---