This article has been archived. It is offered "as is" and will no longer be updated.
After you make changes to a Visio document that is contained in an ODMA Document Management System (DMS), your changes may not be saved after you try to save the changes back to the current document.
This problem occurs in Visio when is managed by a Document Management System (DMS) that uses Open Document Management APIs (ODMA). Visio notifies the DMS of a user's "Save As" request from the Visio File menu. The DMS is tasked with prompting the user for Save As information such as the new file name. If the DMS reports back to Visio to change the Save As operation to a normal Save to save the document to its current file location, Visio notifies the DMS that the document was saved without actually saving the document. When Visio is managed by a Document Management System, the Save As function causes Visio to call the ODMSaveAs API that prompts the DMS to report back to Visio instructions for saving the document. These instructions are communicated back to Visio through the ODMSaveAs arguments. If the DMS sets the NewDocID argument to an empty string, it instructs Visio to save the document to its current file location. Visio follows up as expected by calling the ODMSaveDoc API to inform the DMS that the document was saved. However Visio does not actually save the document.
Service pack information
This problem is corrected in Microsoft Visio 2002 Service Pack 2.
To resolve this problem, obtain the latest service pack for Visio 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
867749 How to obtain the latest Visio 2002 Service Pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The global version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Size File name ------------------------------------------------------ 06-Feb-2003 23:55 907,264 Kb813959-visio2002eng.msp
After the hotfix is installed, the global version of this fix will have the file attributes (or later) that are listed in the following table:
Date Time Version Size File name ------------------------------------------------------ 03-Feb-2003 17:55 10.0.3731.4 68,824 Visio.exe 03-Feb-2003 17:55 10.0.3731.4 6,352,096 Vislib.dll 03-Feb-2003 17:55 10.0.3731.4 646,312 Visres.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Visio 2002 Service Pack 2.
For more information about ODMA specifications, visit the following ODMA SDK Web site: