I've been working with Integration's V12 Database Xtra (http://integration.qc.ca/products/v12director/default.asp), and can highly recommend it to anyone who has to deal with a foreign or otherwise non-standard character set. I was able to create my own search/sort order, word boundaries, etc. So far I've only been using it under Windows. This is not a promotional posting, however. I ran into a snag. Does anyone who is experienced using V12 know how to prevent/control character set remapping in its databases when moving data cross platform? The V12 docs are very well written and talk about how V12 kindly remaps the charset, but I couldn't find any info on how to prevent or control the process. In a db system where one can build one's own definition of the "string" data type, one would expect to be able to control cross-platform remapping, so I suspect that V12 can do it, and I'm just missing something. I've been struggling with this issue with Director itself (because in my dreadful experience, the fontset.txt charset mappings don't work for embedded fonts), and now V12 is doing the same thing to me. Thanks for any tips! Slava [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
