The information in this article applies to:
SYMPTOMS
When using an ODMA application, if a Microsoft Office 2000 program runs a Microsoft Visual Basic for Applications (VBA) macro, the Office program's ODMA AppID is updated to "MS VB" instead of the expected Application ID.
For example, "MSWORD" is sent to the ODMA Connection manager (Odma32.dll). This is a problem for the ODMA-compliant Document Management System, because it can no longer associate which program made the original file I/O calls to the ODMA Connection Manager. RESOLUTIONTo work around this problem, you can prevent this from occurring within an ODMA application as follows:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. Additional query words:
Keywords : |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |