|
Post by George on May 27, 2021 11:33:31 GMT -5
Robert:
First - switching to hex when the found string contains non-printable characters has been true for years. Not a problem.
Second - The error in the message showing the raw input has been there probably since DLM support was added, it's not a 2.5 error.
The second has been corrected.
The retrieve failure is still one of our mysteries. Of course it works fine here. Even when I use your CFG file, it still works fine.
George
|
|
|
Post by George on May 27, 2021 13:12:11 GMT -5
Robert: You're correct, there were two errors in there. After finding the 1st, related to DLM literals, I just figured "That's it".
But a 2nd error affected the found string in general - it was using the wrong translate table.
Now corrected.
Re: RETRIEVE. When using your CFG, and it's retrieve stack, I had no problems. I looked at the table in DB Browser, and it looks fine, it's got the normal 50 entries, and they all look reasonable. I guess you could reset them by exporting the table with CFGMaint, blanking all the entries (or making them all the same) and then Importing it back. But it just doesn't look like there's anything wrong with it.
George
|
|