Xbase++

Upload Text to an FTP Server (StringBuilder)

Demonstrates the Chilkat Ftp2.PutFileSb method, which encodes the text in a StringBuilder and uploads it to a remote path. The arguments are the StringBuilder, the charset, whether to include a byte-order mark, and the remote file path.

Background: The text-oriented upload: assemble a document — CSV, config, JSON — in a StringBuilder and the method handles encoding as it writes. The charset governs the bytes actually stored, and the byte-order-mark flag is useful when a consuming Windows application expects a BOM.

Chilkat Xbase++ Downloads

Download Chilkat for Xbase++

Xbase++

LOCAL nSuccess
LOCAL oFtp
LOCAL oSb
LOCAL nIncludeBom

nSuccess := 0

//  Demonstrates the Ftp2.PutFileSb method, which encodes the text in a StringBuilder and uploads
//  it to a remote path.  The 1st argument is the StringBuilder, the 2nd is the charset, the 3rd
//  selects whether a byte-order mark is included, and the 4th is the remote file path.

oFtp := CreateObject("Chilkat.Ftp2")

oFtp:Hostname := "ftp.example.com"
oFtp:Username := "myFtpLogin"

//  Normally you would not hard-code the password in source.  You should instead obtain it
//  from an interactive prompt, environment variable, or a secrets vault.
oFtp:Password := "myPassword"

nSuccess := oFtp:Connect()
IF (nSuccess == 0)
    ? oFtp:LastErrorText
    oFtp:destroy()
    RETURN
ENDIF

//  Build the text to upload.
oSb := CreateObject("Chilkat.StringBuilder")
oSb:Append("name,quantity" + Chr(10))
oSb:Append("widgets,42" + Chr(10))

//  Upload as UTF-8 without a byte-order mark.
nIncludeBom := 0
nSuccess := oFtp:PutFileSb(oSb, "utf-8", nIncludeBom, "public_html/inventory.csv")
IF (nSuccess == 0)
    ? oFtp:LastErrorText
    oFtp:destroy()
    oSb:destroy()
    RETURN
ENDIF

? "Uploaded text file."

nSuccess := oFtp:Disconnect()
IF (nSuccess == 0)
    ? oFtp:LastErrorText
    oFtp:destroy()
    oSb:destroy()
    RETURN
ENDIF

oFtp:destroy()
oSb:destroy()