We have converted a database to unicode and we need to migrate all our delphi applications.
All datasets have persistent TStringField and this seems to be a big problem because fields in unicode should be TWideStringField. Is there a workaround to avoid to modify all string fields ?
TIA
Sergio Sette
Unicode Migration
Re: Unicode Migration
ODAC components don't have a tool for converting persistent fields from one type to another. Try to make necessary changes directly in .DFM files of your project.
Re: Unicode Migration
Ok, if we can just replace TStringField with TWideStringField in dfm the migration will be not so hard as expected.
Another related question: we noted that using TWideStringField and UseUnicode = True with NON Unicode databases (in our case ITALIAN_ITALY.WE8MSWIN1252) all works as expected (or at least with Italian and German charachters like à, è, â). Can you confirm this ? And, if yes, why not using always TWideStringFiels ?
Best regards
Sergio Sette
Another related question: we noted that using TWideStringField and UseUnicode = True with NON Unicode databases (in our case ITALIAN_ITALY.WE8MSWIN1252) all works as expected (or at least with Italian and German charachters like à, è, â). Can you confirm this ? And, if yes, why not using always TWideStringFiels ?
Best regards
Sergio Sette
Re: Unicode Migration
You can use TWideStringField when working both with Unicode and NON Unicode databases.
Note that when using the property UseUnicode = True, TWideStringField will be automatically created, it is a universal solution
Note that when using the property UseUnicode = True, TWideStringField will be automatically created, it is a universal solution