SQL Server
SQL Server
Create MIME Containing Plain-Text
See more MIME Examples
Calls SetBodyFromPlainText to load plain-text into the MIME body. Also sets the Content-Type header to "text/plain", and the Content-Transfer-Encoding to an appropriate transfer encoding based on the characters found in the text.Chilkat SQL Server Downloads
-- 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 @success int
SELECT @success = 0
-- This example requires the Chilkat API to have been previously unlocked.
-- See Global Unlock Sample for sample code.
DECLARE @mime int
EXEC @hr = sp_OACreate 'Chilkat.Mime', @mime OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Add a few header fields:
EXEC sp_OAMethod @mime, 'AddHeaderField', @success OUT, 'Description', 'this is a test'
EXEC sp_OAMethod @mime, 'AddHeaderField', @success OUT, 'MyId', '123'
DECLARE @textBody nvarchar(4000)
SELECT @textBody = 'This is the plain-text body'
EXEC sp_OAMethod @mime, 'SetBodyFromPlainText', @success OUT, @textBody
EXEC sp_OAMethod @mime, 'GetMime', @sTmp0 OUT
PRINT @sTmp0
-- The MIME should look like this:
-- Description: this is a test
-- MyId: 123
-- Content-Type: text/plain;
-- Content-Transfer-Encoding: 7bit
--
-- This is the plain-text body
-- Note: The Content-Transfer-Encoding may be changed.
-- For example, to use "base64", do this:
EXEC sp_OASetProperty @mime, 'Encoding', 'base64'
-- Show the MIME again, this time using the base64
-- transfer encoding:
EXEC sp_OAMethod @mime, 'GetMime', @sTmp0 OUT
PRINT @sTmp0
-- It should look like this:
-- Description: this is a test
-- MyId: 123
-- Content-Type: text/plain
-- Content-Transfer-Encoding: base64
--
-- VGhpcyBpcyB0aGUgcGxhaW4tdGV4dCBib2R5
--
EXEC @hr = sp_OADestroy @mime
END
GO