Albert,
I ran the SELECT query with and without the "=40" and the results were the same.
The "=40" merely controlled the formatting of the display on the screen.
The fundamental problem is that the syntax works in one case and not the
other. The "&" character is not free standing in either case. It is part
of a variable name. See Razzak's From the Edge article on when
to use a dotted variable vs an ampersand variable.
Jim Bentley,
American Celiac Society 1-504-737-3293
________________________________
From: Albert Berry <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Friday, March 28, 2014 9:19 PM
Subject: [RBASE-L] - Re: Store procedure question
I notice an =40 in your select statement that is not allowed in UPDATE. The =40
is a display width used when SELECTing to the screen only. I have deleted your
prior posts, so I don't remember seeing it in the UPDATE, but if it is there,
take it out and try again.
Albert
On 3/28/2014 10:56 AM, James Bentley wrote:
Mike
>Thanks. I had considered that alternative but I believe there
>may be a glitch in the syntax editor as I should not have to
>code two lines since the following works in a select
statement:
>SELECT (SRPL(&FxTXHqColumn,CHAR(44),NULL,0))=40 FROM
&FxTXHqTable
> WHERE &FxTXHqColumn CONTAINS CHAR(44)
>
>Here is the results of executing that statement:
> (SRPL(TXHqLastName,CHAR(44),NULL,0))
> ----------------------------------------
> Gutierrez
>
>
>Note! The SRPL statement is exactly the same as in my UPDATE
>
>statement. Why does it work in one case and not the other?
>I have decided to open a problem with RDCC.
>
>
