Mensaje
De
03/10/2006 13:24:31
a
03/10/2006 05:52:25
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
ID de la conversación:
01158787
ID del mensaje:
01158978
Views:
39
Hi, Dorin
I have asked about this bug several months ago. It is still present in VFP 9.0 SP1 and as far as I know there is no workaround for it. The only way to avoid it is to set your OS to English.
>>Hi,
>>
>>This BUG is in VFP 9.0 SP1?
>>
>>LOL,
>> I did fight with bug in FP 2.5 for DOS...
>>
>>MartiJ
>>
>
>Unfortunately, yes, it is.
>
>You can easy reproduce it if your CPCURRENT() is different than 1252
>
>Unpack ReportPreview from xsource.zip (frxpreviewform has a long _memberdata)
>Open frxpreviewform class
>Save it (without any changes)
>Open it again
>Choose "MemberData editor" from menu, this will trigger "Invalid XML" error
>Also, all custom properties lose displayed name settings
I have asked about this bug several months ago. It is still present in VFP 9.0 SP1 and as far as I know there is no workaround for it. The only way to avoid it is to set your OS to English.
>>Hi,
>>
>>This BUG is in VFP 9.0 SP1?
>>
>>LOL,
>> I did fight with bug in FP 2.5 for DOS...
>>
>>MartiJ
>>
>
>Unfortunately, yes, it is.
>
>You can easy reproduce it if your CPCURRENT() is different than 1252
>
>Unpack ReportPreview from xsource.zip (frxpreviewform has a long _memberdata)
>Open frxpreviewform class
>Save it (without any changes)
>Open it again
>Choose "MemberData editor" from menu, this will trigger "Invalid XML" error
>Also, all custom properties lose displayed name settings
Grigore Dolghin
Class Software.
Class Software.