(SQL Server) Appending Strings to BinData

Demonstrates appending strings to a BinData..

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

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @binData1 int
    -- Use "Chilkat_9_5_0.BinData" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.BinData', @binData1 OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Append a string using a 1-byte per char encoding
    DECLARE @success int
    EXEC sp_OAMethod @binData1, 'AppendString', @success OUT, 'This is a test', 'windows-1252'
    EXEC sp_OAMethod @binData1, 'GetEncoded', @sTmp0 OUT, 'hex'
    PRINT @sTmp0
    -- The bytes contained within the binData1 (in hex) are: 54,68,69,73,20,69, ...

    DECLARE @binData2 int
    -- Use "Chilkat_9_5_0.BinData" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.BinData', @binData2 OUT

    -- Append a string using a 2-byte per char encoding
    EXEC sp_OAMethod @binData2, 'AppendString', @success OUT, 'This is a test', 'utf-16'
    EXEC sp_OAMethod @binData2, 'GetEncoded', @sTmp0 OUT, 'hex'
    PRINT @sTmp0
    -- The bytes contained within the binData2 (in hex) are: 54,00,68,00,69,00,73,00,20,00,69,00, ...

    EXEC @hr = sp_OADestroy @binData1
    EXEC @hr = sp_OADestroy @binData2


END
GO