During conversion of our customers' data from 2003 to v11 in unicode mode, we did some trick to allow 4D convert data to unicode correctly. It only helps if your data contains only one type of non-roman character.
For instance, most of our users use Traditional Chinese (big5) in 2003. Before conversion, we change the regional setting of the server to Tradition Chinese in our case. Then launch the data in the server with new structure on v11. After the conversion, quit the server and change the regional setting back to English. Launch the server again, all data in Traditional Chinese could be veiwed in new version. However, data in other non-roman character sets couldn't be viewed correctly and requires manual update (re-enter the field). YMMV Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >3) How do I convert the existing text data in records (and indexes) to Unicode? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
