(PowerBuilder) 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

integer li_rc
oleobject loo_Ftp
string ls_RemoteFilePath
string ls_LocalFilePath
integer li_Success

loo_Ftp = create oleobject
// Use "Chilkat_9_5_0.Ftp2" for versions of Chilkat < 10.0.0
li_rc = loo_Ftp.ConnectToNewObject("Chilkat.Ftp2")
if li_rc < 0 then
    destroy loo_Ftp
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// ...
// ...

// Insert this code just before the method call that crashes or hangs.
loo_Ftp.VerboseLogging = 1
loo_Ftp.DebugLogFilePath = "/some/file/path/sftp_debug_log.txt"

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

ls_RemoteFilePath = "..."
ls_LocalFilePath = "..."
li_Success = loo_Ftp.PutFile(ls_LocalFilePath,ls_RemoteFilePath)

// 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 li_Success = 0 then
    Write-Debug loo_Ftp.LastErrorText
    destroy loo_Ftp
    return
end if



destroy loo_Ftp