You are currently offline, waiting for your internet to reconnect

Visio2000: UML Associations and Stereotypes Lost When Saved to Repository

This article was previously published under Q281890
This article has been archived. It is offered "as is" and will no longer be updated.
If you use a Universal Modeling Language (UML) Stereotype element and associate it to a UML element, when you export to the Microsoft Repository, the associations and stereotype information between the elements, and the Stereotype element definitions are lost.
This problem occurs if the UML Model is stored within the Microsoft Repository accessed by the Repodbc.dll (build 2000.0.189.0), which is included with Microsoft SQL Server 2000.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date         Time    Version      Size       File name     --------------------------------------------------------   26-Feb-2001  16:39   5.0.2920.0   524,560    Q281890.exe				
After the hotfix is installed, the following files will have the listed attributes or later:
   Date         Time    Version      Size       File name       ---------------------------------------------------------   21-Feb-2001  16:14   1,511,424  Umlbkgnd.vsl 				

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
After Microsoft released Visio 2000 SR-1, Microsoft released a new version of Repository version 3.0, which was included with SQL Server 2000. This new version of Repository introduced changes to protocols for manipulating and interacting with new datatypes, and changed return codes from Repodbc.dll. These changes revealed the new, unwanted behavior.

The hotfix described in the "Resolution" section of this article does not correct UML solutions that were exported to the Repository before you applied the hotfix. The hotfix only corrects new UML Models that you export to the Repository, after the hotfix files are in place.

To correct UML models that were placed into the Repository before the updated files were in place, you must re-export the original static UML Models to the Repository, and replace the appropriate Model, as noted in Repository Export dialog box.

Article ID: 281890 - Last Review: 10/21/2013 04:49:57 - Revision: 1.5

Microsoft Visio 2000 Service Release 1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB281890