On databases converted from GS/S 32-bit, the conversion script correctly
modifies the superclass of DoubleByteString to MultiByteString, but does
not update the MetaClass properly, leaving it set to CharacterCollection
class. This can cause problems with class method lookup for DoubleByteStrings,
causing #rtErrDoesNotUnderstand (2010) errors, or the execution of incorrect
methods, missing the method defined in MultiByteString class.
To confirm if you are subject to this bug, execute the following:
topaz 1> level 0 topaz 1> run DoubleByteString class superClass
%
The correct response should be:
MultiByteString class
If you find:
CharacterCollection class
Then you have this bug and should execute the following workaround.
Log in as SystemUser, execute the following:
DoubleByteString class _unsafeAt: 1 put: MultiByteString class.
Commit, and log out.
Last updated: 9/19/12