You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Thomas,
I see UnspecifiedOffsetinfo1 and UnspecifiedOffsetinfo1 in POffsetInfoType_String are the max size of the string (one is 2 bigger because consider the parameters MaxLength (i.e. 256) and UsedLength (i.e 254)).
It is curious that sometimes the UnspecifiedOffsetinfo1=254 and UnspecifiedOffsetinfo2=256 and sometime UnspecifiedOffsetinfo1=256 and UnspecifiedOffsetinfo2=254.
If you read the single item obviously this is not a problem.
The text was updated successfully, but these errors were encountered:
In my test with plain string variables (no array) it was always as expected.
I see a difference when there's a Array of WString. Then I get at Offsetinfo1 = 254 (correct) but Offsetinfo2 = 512. But a plain WString in the same datablock gives Offsetinfo1 = 254 and Offsetinfo2 = 256. But this difference comes from padding bytes, which are added in a WString-Array (can be seen in a not-optimized DB).
At least for writing strings the values should be correct, because you need to write the complete length with the string-header.
Hello Thomas,
I see UnspecifiedOffsetinfo1 and UnspecifiedOffsetinfo1 in POffsetInfoType_String are the max size of the string (one is 2 bigger because consider the parameters MaxLength (i.e. 256) and UsedLength (i.e 254)).
It is curious that sometimes the UnspecifiedOffsetinfo1=254 and UnspecifiedOffsetinfo2=256 and sometime UnspecifiedOffsetinfo1=256 and UnspecifiedOffsetinfo2=254.
If you read the single item obviously this is not a problem.
The text was updated successfully, but these errors were encountered: