FiveTech Software tech support forums

... oLbx, .f. ) REDEFINE GET oBusco VAR cBusco ID 400 OF oDlg ; ON CHANGE ( oBusco:Assign(), ; oPaci:Seek( AllTrim(UPPER(cBusco))+; IF( ISALPHA( CHR(nKey) ) .OR. ISDIGIT( CHR(nKey) ) ; .OR. nKey = 32, UPPER(CHR(nKey)), "" ) ), ; oLbx:refresh() ) // REDEFINE BUTTON ID 170 OF ...

... oLbx, .f. ) REDEFINE GET oBusco VAR cBusco ID 400 OF oDlg ; ON CHANGE ( oBusco:Assign(), ; oPaci:Seek( AllTrim(UPPER(cBusco))+; IF( ISALPHA( CHR(nKey) ) .OR. ISDIGIT( CHR(nKey) ) ; .OR. nKey = 32, UPPER(CHR(nKey)), "" ) ), ; oLbx:refresh() ) // REDEFINE BUTTON ID 170 OF ...

... oLbx, .f. ) REDEFINE GET oBusco VAR cBusco ID 400 OF oDlg ; ON CHANGE ( oBusco:Assign(), ; oPaci:Seek( AllTrim(UPPER(cBusco))+; IF( ISALPHA( CHR(nKey) ) .OR. ISDIGIT( CHR(nKey) ) ; .OR. nKey = 32, UPPER(CHR(nKey)), "" ) ), ; oLbx:refresh() ) // REDEFINE BUTTON ID 170 OF ...

Code: Select all  Expand view  RUN

   ? ISUPPER( "Abcde" )    // .T.
   ? ISUPPER( "abcde" )    // .F.
 

Seealso

ISALPHA(), ISLOWER(), ISDIGIT(), LOWER(), UPPER()

Regards.

It is more than 30 years since 1986. Lot has changed since then. For all those who are maintaining data in ANSI, as is the present (default) practice, (x)Harbour default behaviour works perfectly. One option available is to migrate the data to ANSI and use contemporary tools comfortably. In ADS also...

I would just create a separate field in your database where the accents are eliminated and use that for the index key.

I would point out that all the chars in my databases are not based on ANSI but on OEM, MS-DOS CP 850.
Since 1986 with Clipper. All that is put on the screen or printer with my Windows applications,
is translated before with OemToAnsi().

Dear G. N. Rao, I could not use your browser because there is a « syntax error at SHOW » for my xHarbour compiler. Here are lists with my internal browser, printed in pdf : - http://icim.fr.free.fr/test/test-french-dbfcdx-collation-codepage-fr850.pdf - http://icim.fr.free.fr/test/test-french-dbfcdx-...

Mr. Badara Thiam I am sorry, I am unable to agree. If we set codepage correctly, sorting and indexing by (x)Harbour is correct and respects the rules of the language set by the codepage. It is NOT correct that (x)Harbour sorts alphabets by ASCI values. NO. It sorts the alphabets by the language coll...

Great! Can you share the solution, please?

EMG

Solved in great part by insert RDDInit() on the start of main .prg, after reminder by David A. Smith in xHarbour forum. :oops: Upper() continue to return accents in uppercase, but my alphabetic lists are very better. The "é" was after "z" before, now the "é" is before &...

But if ADS is not connected, or if we want change RDD to DBFCDX for example, Upper() of xHarbour is used, who is not compatible with alphabétic order. Because the ASCII codes of all accented chars are after the ASCII code of "Z". This is why it is necessary to "destroy" all accen...

I think ADS would use its own function anyway.

EMG

Because i not found the way to replace Upper() by my own Upper() in xHarbour, and ADS reconize only "Upper" name in indexed keys.
My function Maj() do what Clipper do, and it is not a problem when i don't use ADS. I cannot use ADS only because this.

Why can't you use your own function for this?

EMG