SQL Server

Set the FTP Transfer Type to ASCII

Demonstrates the Chilkat Ftp2.SetTypeAscii method, which sets the FTP representation type to ASCII for subsequent transfers. It takes no arguments.

Note: The local paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.

Background: ASCII mode translates line endings between the client and server conventions (with CrlfMode able to apply further conversion on download). It is a legacy behavior that is rarely wanted today — binary is recommended for essentially every file, text included — and it silently corrupts binary content such as images and archives. Use it only when line-ending translation of plain text is specifically required, and switch back with SetTypeBinary afterward.

Chilkat SQL Server Downloads

Download Chilkat for SQL Server

SQL Server

--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  Demonstrates the Ftp2.SetTypeAscii method, which sets the FTP representation type to ASCII for
    --  subsequent transfers.  It takes no arguments.

    DECLARE @ftp int
    EXEC @hr = sp_OACreate 'Chilkat.Ftp2', @ftp OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OASetProperty @ftp, 'Hostname', 'ftp.example.com'
    EXEC sp_OASetProperty @ftp, '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.
    EXEC sp_OASetProperty @ftp, 'Password', 'myPassword'

    EXEC sp_OAMethod @ftp, 'Connect', @success OUT
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        RETURN
      END

    --  In ASCII mode the endpoints may translate line endings (and CrlfMode can apply additional
    --  conversion).  This is a legacy mode that is rarely needed today; binary (the default) is
    --  recommended for essentially every file.  Use ASCII only when line-ending translation is
    --  specifically wanted, and never for binary files, which it would corrupt.
    EXEC sp_OAMethod @ftp, 'SetTypeAscii', @success OUT
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        RETURN
      END

    EXEC sp_OAMethod @ftp, 'GetFile', @success OUT, 'public_html/readme.txt', 'qa_output/readme.txt'
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        RETURN
      END

    EXEC sp_OAMethod @ftp, 'Disconnect', @success OUT
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        RETURN
      END

    EXEC @hr = sp_OADestroy @ftp


END
GO