HOWTO: Sending a Message in VFP Using Active Messaging

Last reviewed: October 14, 1997
Article ID: Q175052
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0, 5.0a
  • Active Messaging Library, version 1.1

SUMMARY

This article provides two small code samples using Active Messaging from Visual FoxPro.

It is the intention of the author of this article to make you, the developer, aware that you have the option of Active Messaging available to you in order to implement messaging functionality in your applications.

While this article is designed as a mere introduction to demonstrate just the most basic functionality of the Active Messaging Library, you should be aware that the Active Messaging Library is very robust, much more so than the vast majority of Messaging Controls.

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q171440
   TITLE     : Where to Acquire the Active Messaging Library


MORE INFORMATION

This first sample is a minimal scenario providing just enough to construct and send a message:

   * AM_BareBones.PRG
   * ----------------
   *
   *Create a MAPI Session object then Logon. The Logon dialog can be
   *bypassed by providing a valid ProfileName as the first parameter
   *(as a string) to the Logon Method.
   objSession = CREATEOBJECT("mapi.session")
   objSession.Logon

   *Create a new message in the Outbox
   objMessage = objSession.Outbox.Messages.Add

   *Populate a few basic properties of the message
   objMessage.Subject = "This is the subject"
   objMessage.Text = "This is the message text"

   *Add a Recipient to the message we just created and resolve
   objRecip = objMessage.Recipients.Add
   *Alias of who you are sending to
   objRecip.name = "TargetEmailName"
   objRecip.Resolve

   *Send it
   objMessage.Send

   *Clean up then bail
   objSession.Logoff
   RELEASE objRecip, objMessage, objSession
   *EOP: AM_BareBones.PRG

The second sample is similar to the first except that it adds an attachment to the outgoing message. This sample also demonstrates a few alternate ways that the same functionality can be accomplished without using the same code. For instance, logging on and passing a ProfileName instead of getting prompted to enter one, or the slightly different manner in which the recipient is added.

   * AM_Attachments.PRG
   * ------------------
   *
   *Create a MAPI Session object then Logon. The Logon dialog can be
   *bypassed by providing a valid ProfileName as the first parameter
   *(as a string) to the Logon Method as seen below.
   objSession = CREATEOBJECT("mapi.session")
   objSession.Logon("YourProfileName")

   *Create a new message in the Outbox and populate a few basic properties
   objMessage = objSession.Outbox.Messages.Add
   objMessage.Subject = "Visual Fox Active Messaging Sample - Attachments"
   objMessage.Text = "This is the message text."

   *Add an attachment (assumes "myfile.doc" exist in c:\)
   objMessage.Attachments.Add("MyFile.doc", 0, 1, "c:\myfile.doc")

   *Add a Recipient to the message we just created and resolve
   objRecip = objMessage.Recipients.Add("TargetsEmailName") && who it's to
   objRecip.Resolve

   *Send it
   objMessage.Send

   *Clean up then bail
   objSession.Logoff
   RELEASE objRecip, objMessage, objSession
   *EOP: AM_Attatchments.PRG

REFERENCES

MSDN, and OLEMSG.HLP in Platform SDK


Additional query words: Active Messaging
Keywords : vfoxwin ActMsg kbcode
Version : WINDOWS:1.1,3.0,3.0b,5.0,5.0a
Platform : WINDOWS
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.