Results 1 to 7 of 7

Thread: HexToStr DF19 vs DF20

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default HexToStr DF19 vs DF20

    Dear,

    We are migrating the version to 20.0.7.

    In version 19.1.58 we had the following;

    HEX: 19fde9083322f1
    Code:
    //²Ú3"±
    Move (Ascii("")) to iChar // 25
    Move (Ascii("²")) to iChar // 253
    Move (Ascii("Ú")) to iChar // 233
    Move (Ascii("")) to iChar // 8
    Move (Ascii("3")) to iChar // 51
    Move (Ascii('"')) to iChar // 34
    Move (Ascii('±')) to iChar // 241
    Click image for larger version. 

Name:	hex_19.png 
Views:	18 
Size:	10.0 KB 
ID:	15122

    In version 20.0.7 we had the following;

    HEX: 19fde9083322f1
    Code:
    //²Ú3"±
    Move (Ascii("")) to iChar // 25
    Move (Ascii("²")) to iChar // 178
    Move (Ascii("Ú")) to iChar // 218
    Move (Ascii("")) to iChar // 8
    Move (Ascii("3")) to iChar // 51
    Move (Ascii('"')) to iChar // 34
    Move (Ascii('±')) to iChar // 177
    Click image for larger version. 

Name:	hex_20.png 
Views:	19 
Size:	10.1 KB 
ID:	15123

    Help:
    ASCII returns the number of the character according to the Unicode standard. Up until character 127 this matches the ASCII table.

    We understand the new concept, but I was wondering if there is any way to run on the same concept as version 19.1.58 in a specific routine.

    I wanted to try to avoid changing this routine for now.
    Last edited by Gleidson Maia; 12-Jan-2022 at 07:02 PM.
    Regards,

    Gleidson Maia
    Brazil

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •