Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Karl-Heinz" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Wrong Sort Order of Index Date: Fri, 25 Aug 2017 12:58:55 +0200 Lines: 62 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Trace: individual.net Z9R/6HAxYyV80H6ubaroLA7Gr1/B/PpnbNbfXONJ83mOhJou0= Cancel-Lock: sha1:IGBsVysrfw1IYoIJXZPPBMNDy5w= In-Reply-To: X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 Xref: csiph.com comp.lang.clipper.visual-objects:10933 Hi Michael, > I have do some tests: (ADS-12, OEM- und ANSI-Character Set is setting to > GERMAN),l but xHarbour i made a small VO-Test. Depending on that code i get these results: FUNCTION Start() LOCAL oDB AS DBServer LOCAL cPfad AS STRING // makes no differences if sortorder.dbf ist a OEM-Dbf or not // SetCollation ( #windows ) SetCollation ( #clipper ) RddSetDefault ( "DBFCDX" ) cPfad := "D:\test\" IF File ( cPfad + "SOrtorder.cdx" ) FErase ( cPfad + "SOrtorder.cdx" ) ENDIF oDB:= DbServer { cPfad + "SOrtorder.dbf" } oDB:Createorder ( "OrderID", cPfad + "SOrtorder.cdx", "Upper(ID)" ) oDB:Close() RETURN NIL #clipper aaa aaa-bab aaa-bbc aaa-bcb abc abd #Windows aaa-bab aaa-bbc aaa-bcb aaa abc abd But there might be another problem.No matter if the index is created using #clipper or #windows a seek shouldn´t fail. Maybe later on, after creating the index, Jürgen switches from #windows to #clipper ? Didn´t try that, but i guess that a seek fails - maybe not always - in such cases ? regards Karl-Heinz