I'm seeing some odd behavior in the Insert function. First, the code segment:
AFEMItem.Insert((int)XXX_amcs.ConvData,iPos,sTemp);
By the time this is executed, AFEMItem has several attributes defined.
(int)XXX_amcs.ConvData resolves to 26;
iPos is set to 1;
sTemp has a string value (e.g., 12345.P)
Attribute 26 of AFEMItem is blank before that Insert; after, it contains the value in sTemp followed by a Value Mark and ... well, nothing.
That has the undesirable side effect of looking like an empty value in a MV'd string.
I could add logic that says, in effect, "if the entire attribute is null then Replace, else Insert" - but that seems clunky. Also, that's not how the INSERT functionality works in UniBasic.
Any ideas?
Note: I think I'm using a very recent version of U2 Toolkit for .NET: 1.2.0.1229