PC Forms: No Error Returned by MEFWriteItem() Function

Last reviewed: October 25, 1994
Article ID: Q105177
The information in this article applies to:
  • Microsoft Electronic Forms Designer, version 1.0, running with Microsoft Mail for PC Networks, version 3.0 or 3.2

SYMPTOMS

With version 1.0 of Microsoft Electronic Forms Designer, you can use the MEFWriteItem() function to add information to the E-Form package. When you use MEFWriteItem() to add a binary file to the package by setting the type parameter equal to MEF_BINARYFILE, unexpected return values may be generated. For example, if an invalid path is given to the binary file to be attached, the MEFWriteItem() function will return MEF_OKAY, as if the file were successfully attached.

However, when the message is sent and the package is saved, a "File Open Failed" error will be presented.

CAUSE

The Microsoft Electronic Forms Designer does not take a snapshot of the file for the binary file type. Because of this, it does not try to open the file when it is written to the package. Instead, it attempts to open the file when the package is saved. This is why the error "File Open Failed" is returned when the package is saved, as opposed to when the file is attached using MEFWriteItem().


Additional reference words: 1.00
KBCategory: kbprg
KBSubcategory: MailPCForms


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