Home > Back-end >  Why ClientDataSet -> XmlData in XP and inconsistent results under Windows 7 64?
Why ClientDataSet -> XmlData in XP and inconsistent results under Windows 7 64?

Time:09-18

I made a small example of access database BCB6
Memo1 - & gt; Text=ClientDataSet1 - & gt; XMLData;
The same procedure, under XP and running under the Windows 7 64, results differ
Under XP type String into a String under Windows 7. The uni type
XP under normal Chinese characters, Chinese characters under Windows 7 garbled
MIDAS. DLL file version,
Experts can help to solve,

CodePudding user response:

Try to upgrade to higher version and 2009 support Unicode character set,

CodePudding user response:

Only upgrade Midas. DLL file

CodePudding user response:

refer to the second floor caidaolee response:
upgrade only Midas. DLL will you


Don't understand ~

CodePudding user response:

Upgrade with FDMemTable

CodePudding user response:

Saved in the database is fixed character,
You use String under xp display normal, I guess you use AnsiString showed normal,
You are saved in the library are Ansi type of character encoding,
Now you are under the Windows 7 to show with Unicode, affirmation is garbled,
There are two methods:
1, continue to use under Windows 7 AnsiString to display,
Before 2, with Unicode encoding conversion,
  • Related