Paradox Community
Search:

 Welcome |  What is Paradox |  Paradox Folk |  Paradox Solutions |
 Interactive Paradox |  Paradox Programming |  Internet/Intranet Development |
 Support Options |  Classified Ads |  Wish List |  Submissions 


Paradox Programming Articles  |  Beyond Help Articles  |  Tips & Tricks Articles  


Language Drivers - Extended Characters - Queries In ObjectPAL
© 2002 Ingerid Skavdal


With a lot of help from Liz, and from documentation given by Bertil:

If you experience problems getting queries to match extended characters, check out the following (tested in ver. 10):

1. Define your language driver in the BDE. Documentation tells you this is automatically set according to the language driver set in Windows. At least in my system this is not so, it's always set to 'ascii' ANSI.

The language driver set in System > INIT is the one you get by getLanguageDriver(). This is the one Paradox is supposed to use when converting queries. Which obviously is not quite so.

Drivers > Native > Paradox gives default driver for a new table. Set them both to the language driver you desire.

And as I found, both in BDE 5.01 and BDE 5.11, any NorDan driver set in System > INIT will give you the system driver ANSINOR4, that is Pdox ANSI Nordan4! Accordingly I chose to use this driver. the others may work as well.

2. When drivers set correctly in the DBE, you use setLanguageDriver to set how the search criteria is to be converted. You would believe setLanguageDriver("Pdox ANSI Nordan4") would work. It does not, at least not always.

Instead, immediately before the executeQuery set the language driver "to itself".
qbeVar.setLanguageDriver(getLanguageDriver())
This works.

3. Your criteria may still not match. If you keyed in the records under a different language driver, the conversion will not work. Even if those records do not have any extended chars in them!

Convert the records by copying the table, empty the table, restructure it to the correct language driver, and then add the records back from the copy. (If this won't work, try exporting to another format and reimport.)

If records are keyed into the same table under different language drivers, you will see inconsistent behaviour in Paradox. Add a breakpoint, or a comment, and what previously matched with a wrong character, won't match at all. This makes testing difficult. Take it as a warning about your tables being inconsistent.


Discussion of this article


 Feedback |  Paradox Day |  Who Uses Paradox |  I Use Paradox |  Downloads 


 The information provided on this Web site is not in any way sponsored or endorsed by Corel Corporation.
 Paradox is a registered trademark of Corel Corporation.


 Modified: 15 May 2003
 Terms of Use / Legal Disclaimer


 Copyright © 2001- 2003 Paradox Community. All rights reserved. 
 Company and product names are trademarks or registered trademarks of their respective companies. 
 Authors hold the copyrights to their own works. Please contact the author of any article for details.