>> the code once more revealed what the problem was. The syntax errors were occurring in places where there were string constants that contain characters in the upper-ASCII range -- which are often used as "lead-in" characters for double-byte sequences. Essentially what was happening was whenever the character immediately preceding the closing quote was being intepreted as a "lead-in" for a double-byte character, the closing quote would get "eaten" -- thus resulting in the syntax error.
>
> So you padded it with an extra character, or what was the solution?
We side-stepped the problem by using CHR() (rather than entering the string directly with ALT+nnn). For example, wherever we had "©" we simply used CHR(169) instead. And of course, we not only needed to change the PRGs, but also in SCXs, FRXs, DBCs, etc...
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only