Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
Warning: DBISAM and Vista with german lanugage tables |
Tue, Dec 25 2007 10:26 AM | Permanent Link |
Rolf Frei eicom GmbH | At first see my other thread: "Vista and TDBISAMTable.Lookup not working?!"
After many hours of checking DBISAM 3 source what realy is going on here. I had found the reason of not anymore working filters under Vista with german tables. The Prblem is the FCharMap wich gets now just strange entrires: So teh ASCII char 179 gets sortet as teh first character in the Charmap, just below ASCII 0. You can see the CharMap under XP here: http://www.eicom.ch/rolf/Charmap_XP.png You can see the CharMap under Vista here: http://www.eicom.ch/rolf/Charmap_Vista.png As the lowest Char isn't the ASCII 0 value the filtering is broken under Vista by this. What I did now to fix this in DBISAM 3, was to copy the same routine from DBISAM 4 which does only insert and sort the cahracters above 31. This way the lowest character in the list will be ASCII 0 everytime. With this modified routine the filters do work again under Vista. But there is still a serious probem for us german users with german tables: Under Vista the words: 'HÜBNER' and 'HUEBNER' gets handled as teh same. So CompareString on this two words gives CSTR_EQUAL back, which is completly wrong. As Such DBISAM will raise an dublicated Key error, if this values are used in any unique key. But this is a so bad thing, as it not only affects DBISAM 3/4/5 but any delphi applications. TStringList uses that windows call too and as such the search für HUEBNER in the list will return the wrong entry, if there is a HÜBNER too in the stringlist. There was an conversation with Mr. Kaplan a programmer from Microsoft, who has confirmed that bug in Vista and had fixed it for SP1, but lately he was forced to remove that fix from SP1 again. With other words: We german users will have a big problem with our applications under Vista, as MS is not willing to fix ths wrong behaviour. That sucks!!! Here you can see the Blog from MIchael S. Kaplan about this stuff: http://blogs.msdn.com/michkap/archive/2007/05/05/2430935.aspx http://blogs.msdn.com/michkap/archive/2007/09/08/4831056.aspx |
Tue, Dec 25 2007 11:35 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Rolf
Having read those two posts all I can say is you have my sympathy. My interpretation was 1. we screwed up 2. we thought we figured out how to fix it 3. fixing it might screw other things up 4. we ain't bothering I do wish there was a genuine alternative to the MS version of Windows they might then start to pay some attention to "little" issues like this. And to say "I think people will be able to live with in the end" is arrant nonsense. Roy Lambert |
Thu, Dec 27 2007 2:10 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Rolf,
<< After many hours of checking DBISAM 3 source what realy is going on here. I had found the reason of not anymore working filters under Vista with german tables. The Prblem is the FCharMap wich gets now just strange entrires: So teh ASCII char 179 gets sortet as teh first character in the Charmap, just below ASCII 0. >> See my reply in the other thread. Thanks for tracking this down, however. You've provided a lot more information on this then I have been able to provide so far. << There was an conversation with Mr. Kaplan a programmer from Microsoft, who has confirmed that bug in Vista and had fixed it for SP1, but lately he was forced to remove that fix from SP1 again. With other words: We german users will have a big problem with our applications under Vista, as MS is not willing to fix ths wrong behaviour. That sucks!!! >> Yes, it does. I can understand changing the sorting in order to fix a problem. But to change it and cause a problem, and then not fix it, is really bizarre. And, checking the sort version really doesn't solve anything for us because we cannot simply just reindex tables due to the fact that each client application could be running on a different version of the OS. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |