Re: OPO EXEC SQL Query
Date: 1996/01/23
Message-ID: <mikek-2301961240210001_at_franklin-tty12.jvnc.net>#1/1
In article <4dkfkm$r2r_at_nntp.interaccess.com>, sista_at_links.com (Kasu Sista) wrote:
> > gordonh_at_acslink.net.au (Gordon E. Hooker) wrote:
> >
> >EXEC SQL select named into :vQty from platformline where platformid =
> >:vPlatformID and model like :vModel (This would all be on one line)
>
>
> You can't use bind variables in the EXEC SQL statements. Everything in
> here must be resolved at compile time. All OPO does is pass the string
> to the backend. Whatever you must have meaning to the backend. You
> could a build a string in a seperate string variable and use EXEC SQL
> on that string. But it WILL NOT work for select statements. But it
> will work for INSERT, DELETE and UPDATE. This is a feature or a bug I
> don't know. But that is the way it is.
Bind variables work fine in EXEC SQL SELECTs. This is in a button on my form:
months = 12
EXEC SQL SELECT periodname INTO :thename FROM periodlength WHERE
periodmonths = :months
field1.value = thename
The word "Annually" appears up in the field, just as expected.
The problem must be elsewhere - Gordon, if you're still having problems, please repost the question. I had only saved Kasu's reply.
Michael Kranzdorf mikek_at_krt.com Kranzco Realty Trust http://www.krt.com 610.941.9292Received on Tue Jan 23 1996 - 00:00:00 CET