(DataFlex) JSON UpdateNumber vs UpdateInt

Demonstrates UpdateNumber vs UpdateString.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoJson
    Boolean iSuccess
    String sTemp1

    Get Create (RefClass(cComChilkatJsonObject)) To hoJson
    If (Not(IsComObjectCreated(hoJson))) Begin
        Send CreateComObject of hoJson
    End

    // If a number is too large for a 32-bit signed integer, then call UpdateNumber instead of UpdateInt.
    // The large integer is passed to UpdateNumber as a string, but in the JSON it will be an integer.

    // For example:
    Get ComUpdateNumber Of hoJson "largeNumber" "6884556842" To iSuccess

    // If the integer is small enough for a 32-bit signed integer, then use UpdateInt:
    Get ComUpdateInt Of hoJson "reasonableInt" 123456 To iSuccess

    Set ComEmitCompact Of hoJson To False
    Get ComEmit Of hoJson To sTemp1
    Showln sTemp1

    // The output:
    // Notice the large number passed as a string does not have quotes in the JSON

    // {
    //   "largeNumber": 6884556842,
    //   "reasonableInt": 123456
    // }


End_Procedure