BUG: Outlook Loads Custom Form Messages with Attachments

Last reviewed: March 6, 1998
Article ID: Q181940
The information in this article applies to:
  • Exchange Development Kit (EDK), versions 4.0, 5.0
  • Microsoft Outlook 8.03

SYMPTOMS

If you use a custom form to create a message that has an attachment, the Microsoft Outlook 97 client loads the custom form into memory when you right click the message in the client. If there is no attachment, or if you use the Microsoft Exchange 5.0 client, the form is not loaded into memory.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Outlook 97 (8.03.4269) for Windows 95 and Windows NT 4.0.

MORE INFORMATION

The form is loaded into memory and can cause code to run that otherwise would only run as a result of a menu choice from the user.

Steps to Reproduce Behavior

  1. Create a MAPI custom form that allows management of attachments and register it in the system registry.

  2. Run Outlook 97 and Task Manager.

  3. On the Compose menu, click Choose Form.

  4. Select your MAPI custom form from Personal Forms, and then click OK.

  5. Attach a file to the message using your form's file attachment mechanism.

  6. Post to post the message to the current folder. (At this point your form will be listed as an active process in the Task Manager process view.)

  7. End your form process in the Task Manager. (This can also be done by exiting and logging out of Microsoft Outlook.)

  8. Right click the newly posted message and do not make any choices from the menu.

  9. Switch to the Task Manager to see that your MAPI form is now loaded in memory again even though you have not done anything to invoke the form.


Additional query words: ol97
Keywords : ExchExt MAPIForm
Version : WINDOWS:4.0,5.0,8.03
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbpending


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: March 6, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.