|
|
Post by George on May 11, 2022 12:00:59 GMT -5
Robert: Almost forgot this one, and I couldn't spot the posting whee you reported it.
The NFIND search routine has had the delimited search option added. It looks like it was simply 'forgotten' when D'type literals were implemented.
George
|
|
|
|
Post by George on May 13, 2022 15:26:52 GMT -5
Looks fine here. I'm looking at 22131, what version for you?
George
|
|
|
|
Post by mueh on May 14, 2022 0:01:03 GMT -5
Robert: Look in Profile for CASE T or in status bar Box 7 .
I had in Profile CASE without T or C (blank) which created this Problem .
Setting it to CASE T solved problem .
Hope this helps
|
|
|
|
Post by George on May 14, 2022 11:49:06 GMT -5
Guys: I'll check out how CASE is managed. I tried Roberts test and it all worked fine, looking for X or NX lines. But I did this before reading the post further and seeing the CASE comments. And I was using simple D"(|)" string, which wouldn't be affeted by CASE. I'll go do some more testing.
George
[UPDATE]
OK, it still works fine (assuming CASE is set correctly)
But better is the fact that I found where CASE gets corrupted into a "D". There's code in Profile loading that tried to validate various Profile vaiables, and reset any with invalid values. This was added a few yeas ago. The validation of CHANGEMODE (the CS|DS choice) was obviously cut/pasted from the immediately prior CASE code. Guess what variable didn't get modified after the paste.
[/UPDATE]
|
|
