Using the FTP Session Log

Download 32-bit Chilkat FTP2 ActiveX (.msi)

Download All 32-bit Chilkat ActiveX Components (.zip)

Download All 64-bit Chilkat ActiveX Components (.zip)

The Chilkat FTP component can keep a session log if the KeepSessionLog property is turned on. This is helpful in debugging problems. Chilkat support will usually ask for a session log when working to resolve your problem, because it contains a log of the exact commands sent to the FTP server, and the exact responses received.

LOCAL loFtp
LOCAL lnSuccess
LOCAL lcLocalFilename
LOCAL lcRemoteFilename

loFtp = CreateObject('Chilkat.Ftp2')

*  Any string unlocks the component for the 1st 30-days.
lnSuccess = loFtp.UnlockComponent("Anything for 30-day trial")
IF (lnSuccess <> 1) THEN
    =MESSAGEBOX(loFtp.LastErrorText)
    QUIT
ENDIF

loFtp.Hostname = "www.example-code.com"
loFtp.Username = "example-code.com"
loFtp.Password = "****"

*  Set the KeepSessionLog property in order to keep a session log.
*  The session log will continuously grow in memory.  The
*  ClearSessionLog method may be called to clear it.  The session
*  logging may be turned on/off at any point.
loFtp.KeepSessionLog = 1

*  Connect and login to the FTP server.
lnSuccess = loFtp.Connect()
IF (lnSuccess <> 1) THEN
    =MESSAGEBOX(loFtp.LastErrorText)
    QUIT
ENDIF

*  Change to the remote directory where the existing file is located.
lnSuccess = loFtp.ChangeRemoteDir("junk")
IF (lnSuccess <> 1) THEN
    =MESSAGEBOX(loFtp.LastErrorText)
    QUIT
ENDIF

*  To clear the SessionLog at any point, call ClearSessionLog:
*  call ftp.ClearSessionLog();

*  Append moreHamlet.txt to hamlet.txt on the FTP server.

lcLocalFilename = "moreHamlet.txt"

lcRemoteFilename = "hamlet.txt"

lnSuccess = loFtp.AppendFile(lcLocalFilename,lcRemoteFilename)
IF (lnSuccess <> 1) THEN
    =MESSAGEBOX(loFtp.LastErrorText)
    QUIT
ENDIF

loFtp.Disconnect()

*  Display the entire session log:
? loFtp.SessionLog

=MESSAGEBOX("File Appended!")