Microsoft KB Archive/238895

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:09, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


WD2000: Running VBA Macros Causes the AppID to Return "MS VB" Instead of Application Identifier

Article ID: 238895

Article Last Modified on 10/12/2005



APPLIES TO

  • Microsoft Word 2000 Standard Edition



This article was previously published under Q238895

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.

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.

RESOLUTION

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:

245025 OFF2000: How to Obtain and Install Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a)


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.


STATUS

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.

MORE INFORMATION

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

212398 WD2000: Word 2000 Supports ODMA



Additional query words: pcdocs

Keywords: kbbug kbfix kbqfe kbhotfixserver KB238895