PRB: ActiveX MAPI Control 5.0 Causes Memory ErrorsLast reviewed: November 17, 1997Article ID: Q175768 |
The information in this article applies to:
SYMPTOMSWhen you add a MAPISession control version 5.0 or a MAPIMessages control version 5.0 to a form and then edit the (Messaging Application Programming Interface) MAPI control properties, a memory corruption error appears.
RESOLUTIONOne possible resolution is to copy the older Msmapi32.ocx version 1.0.2815 from another computer that is currently running Visual FoxPro version 5.0 or extract the file from the Visual FoxPro 5.0 install disks. For additional information on using the extract utility, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q135518 TITLE : HOWTO: Copy Files from Cabinets on DMF-Formatted DisksNOTE: This resolution will only work as long as another application does not install version 5.0 of the Msmapi32.ocx over version 1.0.2815. These applications may include Visual Basic version 5.0, Visual FoxPro for Windows version 5.0a or an executable file created by one of these applications. NOTE: This error has not been corrected in Service Pack 1 or Service Pack 2.
STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONOnce you try to edit or make changes to any of the MAPISession control or MAPIMessages control specific properties, the following error is displayed:
OLE Idispatch exception code 0 from MAPISession: Property is write-only.-or-
OLE Idispatch exception code 0 from MAPIMessages: Property is write-only.This will not prevent the control from being edited. Click OK and then right-click the control to display the short-cut menu. Choose MAPISession or MAPIMessage Properties to open the Property Pages dialog box. Change one of the properties then click Apply or OK. In Windows 95, the following error message appears:
This program performed an illegal operation and will be shut down.After clicking the Details push button, the following message appears:
VFP caused and invalid pagefault in module KERNEL32.DLL at <register address>.In Windows NT 4.0, the following error appears:
An application error had occurred and an application error log is being generated. VFP.EXE Exception: access violation.NOTE: If you get this error multiple times, the error log file may get larger. You may delete the User.dmp file to free up the space used by this log file.
Steps to Reproduce BehaviorThe following two methods reproduce the application error. Method 1:
Keywords : FxinteropOcx vfoxwin AXSDKControls Version : WINNT:97 Platform : winnt Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |