Re: Concatenation operator in embedded SQL statements in 4GL

Jake, I ran into the same problem a few months back. When I called tech support they told me that was the way it was designed to behave and not a bug. (I have version 6.00). They also mentioned that there were no plans to change it to work. So I guess we will just have to do the prepares/declares/ open/fetch/close/free stuff every time we want to concatonate something. --- ,-, |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ======= ___|| | | ----- //_ || | CANNON EXPRESS | ---- ,-----'| ~ | | | -- |o-----|__ |--`======_______________________________======___| ~~~~~~~~ `-(*)--===~~~~~~(*)(*)| (*)(*)| ------- ------------------------------------------------------------------------- Joseph Cullipher |E-mail: joseph@cannonexpress.com PO Box 364 |opinions express are those of my own and Springdale, AR 72764 USA |don't necessarily reflect those of my company ------------------------------------------------------------------------- On Mon, 9 Jun 1997, Jacob Salomon wrote: } Hi Family, } } I just tried the following in a 4GL program: } } select col1 || col2 } into myvariable } from some_table } } The 4GL compiler actually generated a syntax error for this! >;-( I had } to go through the PREPARE/DECLARE/OPEN/FETCH rigmarole. } } Considering that the || concatenation operator has been available in the } engine since 4.1 or so, I find it incredible that the 4GL 6.05 syntax } checker can't handle it. } } Anyone know if this is a known bug? Or some outstanding feature request? } It certainly was not expected behavior! } } Thanks. } } -- } -- Jake (In pursuit of undomesticated aquatic avians) } } +----------------------------------------------------------+ } |Aside from that, how did you enjoy the play, Mrs. Lincoln?| } +----------------------------------------------------------+ }