Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Different indexed table browse result in WIN XP and 7
Message
De
09/06/2018 09:55:35
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
08/06/2018 12:34:22
Reza Meamar
Homa Programming Group
Shiraz, Iran
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Versions des environnements
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP3
Network:
Windows XP
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01660642
Message ID:
01660651
Vues:
59
>Dear Cetin Basoz
>
>Suppose I have a table with two fields, PName and EName. The contents of the field Pname is customer name with the Persian (or Arabic) characters and the contents of the field Ename is same names in English.
>The following setting should be made at the beginning of the program to properly index Persian names.
>SET COLLATE TO "ARABIC"
>
>I indexed the table based on Pname and Ename.
>I have put this file in a shared folder on windows XP.
>I run the following commands:
>
>SET OREDR TO TAG PNAME
>BROWSE
>
>SET ORDER TO TAG ENAME
>BROWSE
>
>So everything is right here.
>
>But if I connect to the shared folder with a Windows 7 client, the following result is achieved.
>
>SET OREDR TO TAG PNAME
>BROWSE ( wrong result )
>
>SET ORDER TO TAG ENAME
>BROWSE ( Correct result )
>
>Now if I put my table in a shared folder on windows 7 and reindex it, all results is correct. On windows 7 and from windows XP client.
>
>Why is this happening?

I have no idea. I don't use any collating other than Machine. I know you get erroneous results with collate Turkish and thus I never trust collate.
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform