(DataFlex) Ftp2 Debug Log File Path

Demonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs.

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

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoFtp
    String sRemoteFilePath
    String sLocalFilePath
    Boolean iSuccess
    String sTemp1

    Get Create (RefClass(cComChilkatFtp2)) To hoFtp
    If (Not(IsComObjectCreated(hoFtp))) Begin
        Send CreateComObject of hoFtp
    End

    // ...
    // ...

    // Insert this code just before the method call that crashes or hangs.
    Set ComVerboseLogging Of hoFtp To True
    Set ComDebugLogFilePath Of hoFtp To "/some/file/path/sftp_debug_log.txt"

    // Make the call that crashes or hangs,
    // for example, if the method is PutFile:

    Move "..." To sRemoteFilePath
    Move "..." To sLocalFilePath
    Get ComPutFile Of hoFtp sLocalFilePath sRemoteFilePath To iSuccess

    // Note: If the method returns control to your application code, then it did not crash within Chilkat.
    // The DebugLogFilePath property causes all information that would be recorded in the LastErrorText to be emitted to the
    // log file (with immediate file write flushing, i.e. no buffering).  Thus, in a crash situation,
    // the log file will contain information up to the point of the crash.

    If (iSuccess = False) Begin
        Get ComLastErrorText Of hoFtp To sTemp1
        Showln sTemp1
        Procedure_Return
    End



End_Procedure