Here's a curious:
The following code worked last November:
UPDATE SeqTbl SET SPCME = NULL WHERE SPCME > (CHAR(127))
This was used to clean up some data in a conversion to 7.6, some rows
had one or more extended ASCII characters starting in the first position
of text columns.
I tried it last night (1/18/10) and got a "no rows were found" message,
although browsing the table displayed a number of rows with extended
ASCII characters in the column.
I tried the following:
BROWSE (SGET(SPCME,1,1)) FROM SeqTbl
It works, showing the correct standard or extended character.
BROWSE ALL FROM SeqTbl WHERE SPCME = (CHAR(255))
Works, showing rows with a single ASCII 255, a Latin small letter y with
diaeresis
BROWSE ALL FROM SeqTbl WHERE (SGET(SPCME,1,1)) = (CHAR(255))
Works, showing rows with single & multiple ASCII 255.
However,
BROWSE ALL FROM SeqTbl WHERE SPCME > (CHAR(127))
BROWSE ALL FROM SeqTbl WHERE (SGET(SPCME,1,1)) > (CHAR(127))
No rows exist
It seems ">" and "<" are no longer valid, only "=" works with the CHAR
function.
Was I just lucky in Nov or was there a subtle change in syntax?
Is there a db setting that would affect this?
Currently ver 7.6.8.30111
Tnx,
Doug
