>If I have a SQLPREPARE() statement such as:
>
>SQLPREPARE('select na_id, na_liid from list','foobar')
>
>and I want to parse it as follows:
>
>SQLPREPARE('select na_id, ;
>na_liid ;
>from list', ;
>'foobar')
>
>it will compile but will not execute.
>
>If I have a SQLPREPARE() statement such as:
>
>SQLPREPARE('select na_id, na_liid from list','foobar')
>
>and I want to parse it as follows:
>
>SQLPREPARE(''select na_id, ' + ;
>'na_liid' + ;
>'from list,'' +, ;
>'foobar')
>
>it too will compile but will not execute.
>
>Is there a way to parse long SQLPREPARE() statements to make them more readable and printable. Or am I parsing it incorrectly?
>
>Bob
>
>it will compile but will not execute.
SQL is picky about the use of single and double quotes. For example:
select oddfieldname as "GoodFieldName"
has to have the output field name in full quotes. But
...where somefield = 'somevalue'
needs to be in single quotes. Most likely your problem lies in how and where you use which set of quotes.
Mark McCasland
Midlothian, TX USA