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.

In ODMA-compliant products like PCDOCS, when an Office application AppID is set to "MSVB" and saved, these changes do not show up within the list of available documents/edits because "MSVB" is not associated with a product installed on the system or through the ODMA application. Because the changes are not listed, this could result in a perceived loss of document updates, when in fact they are saved for the "MSVB" application.

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base: To temporarily work around this problem, you can prevent this from occurring within an ODMA application as follows:

• Remove any Auto VBA macros or disable macros when opening the document.
• Remove any UserForms from the Normal.dot template.

Additionally, it may help to open or save documents before running Visual Basic for Applications macros.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2000 SR-1/SR-1a.

For additional information about Microsoft Word and document management systems, click the article number below to view the article in the Microsoft Knowledge Base: