MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2003

RE: qry manager queries and character replacement variables



fixed

Richard,

More fun with "'"'s :)  Remember, you gotta build an extra layer of
apostrophe's before you pass it in.....  

ORIGORG   = '"' + &A5 +'"'

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Richard B Baird [mailto:rbaird@esourceconsulting.com]
Sent: Friday, January 17, 2003 9:32 AM
To: midrange-l@midrange.com
Subject: qry manager queries and character replacement variables


hey all,

i'm trying to run a QM query from a CLP, passing it replacement variables.

the manual only gives examples using replacement variable while comparing
to numeric fields - here is the sample they gave:

SELECT DEPT, NAME, JOB, SALARY, COMM
          FROM    &TABLE
          WHERE DEPT >    &COND1
          ORDER BY DEPT, NAME

- dept is numeric, the replacement variable = '10'.

i'm trying to pass a char value ('CRI301'), and compare to an alpha field
in the file like this:
...
 and     ORIGORG   = &A5
..or..
 and     ORIGORG   = '&A5'

if I put quotes around the variable, it treats it as a constant and
compares the field to '&A5'.
if i don't put quotes, it replaces the value, but the sql interpreter
treats it as if it's a column in the file.

can someone tell me how this is done?

Thanks,

Rick

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact