Article ID: 938794
Article Last Modified on 9/18/2007
APPLIES TO
- Microsoft Office Visio 2003 Service Pack 3
- Microsoft Office Visio Professional 2003
- Microsoft Office Visio Standard 2003
SUMMARY
Microsoft has released a service pack for Microsoft Office Visio 2003 that contains fixes for Visio 2003. This article describes the issues that are fixed in Visio 2003 by Microsoft Visio 2003 Service Pack 3 (SP3).
INTRODUCTION
Visio 2003 SP3 provides the latest updates for Visio 2003. Visio 2003 SP3 contains security enhancements, stability improvements, and performance improvements. Some fixes that are included with Visio 2003 SP3 were previously released in Microsoft Office Visio 2003 Service Pack 2 (SP2) or in separate updates. Visio 2003 SP3 combines the previously released fixes into one update.
For more information about Visio 2003 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
923620 Description of Visio 2003 Service Pack 3
MORE INFORMATION
List of issues that the service pack fixes
Visio 2003 SP3 fixes the Visio 2003 issues that are described in the following hotfix packages:
909912 Description of the Visio 2003 post-Service Pack 2 hotfix package: March 24, 2006
915747 Description of the Visio 2003 post-Service Pack 2 hotfix package for the German version of Visio 2003: May 23, 2006
915748 Description of the Visio 2003 post-Service Pack 2 hotfix package for the Chinese (Traditional) version of Visio 2003: May 23, 2006
921209 Description of the Visio 2003 post-Service Pack 2 hotfix package: August 1, 2006
925904 Description of the Visio 2003 post-Service Pack 2 hotfix package: November 14, 2006
928673 Description of the Visio 2003 post-Service Pack 2 hotfix package: January 8, 2007
This service pack also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
- You cannot find a local Visio shape that has a text string that contains more than five characters
When you use a text string that contains more than five characters, such as "square," to search for a local Visio shape, the shape is not found. - You cannot reverse-engineer a Microsoft SQL Server 2005 database or a Sybase 11 database
When you try to reverse-engineer a SQL Server 2005 database or a Sybase 11 database, the connection to the database fails unexpectedly. - Extended data in a Microsoft Office Visio 2007 diagram is not displayed as expected in Visio 2003
In Visio 2003, you open a Database Modeling diagram that was saved in Visio 2007. If the diagram contains extended data, such as Japanese characters, the extended data is not displayed as expected. - The Visio Drawing control does not appear when you open a diagram in Windows Internet Explorer 7
When you open a Visio 2003 diagram that contains the Visio Drawing control in Internet Explorer 7, the control does not appear. - Column notes do not appear when you try to reverse-engineer a SQL Server 2005 database
When you try to reverse-engineer a SQL Server 2005 database, column notes do not appear. - Forms controls in a C# project do not appear when you try to reverse-engineer the project
When you try to reverse-engineer a C# project, forms controls that are contained in the project do not appear in the Model Explorer. - Properties for a Microsoft Visual Basic control are not saved when you try to reverse-engineer a Visual Basic project
When you try to reverse-engineer a Visual Basic project, properties for the Visual Basic controls are not saved. - A hyperlink that is saved in a Visio drawing does not work in Internet Explorer 7
In Visio 2003, you save a drawing that contains a hyperlink as a Web page. If the Web page uses the default Vector Markup Language (VML) output format, and if you open the Web page in Internet Explorer 7, the hyperlink does not work when you click it. Instead, you receive an error message that resembles the following error message: - Changes may not be saved when you change a Visio diagram on a computer that is running Windows Vista
You change a Visio diagram on a Windows Vista-based computer. If you then exit Visio before you save the changes, you are not prompted to save the changes.
This issue occurs when Windows or Visio is exited by using the WM_QUERYENDSESSION message that contains the LPARAM parameter. For example, this condition occurs when you install an update or a hotfix. - The AutoRecover feature is enabled unexpectedly when you start Visio
You disable the AutoRecover feature in Visio 2003. However, the AutoRecover feature is enabled unexpectedly when you start Visio 2003.
This issue occurs when Windows or Visio is exited by using the WM_QUERYENDSESSION message that contains the LPARAM parameter. For example, this condition occurs when you install an update or a hotfix. - You receive an error message when you restart Visio after a diagram is recovered by using the AutoRecover feature
Consider the following scenario. You enable the AutoRecover feature in Visio 2003. You change a diagram, and the AutoRecover feature runs. In this scenario, you receive an error message when you restart Visio.
This issue occurs when Windows or Visio is exited by using the WM_QUERYENDSESSION message. For example, this condition occurs when you install an update or a hotfix.
Note If you click Cancel when you receive the error message, Visio recovers the changes to the diagram. - Items in a list do not appear in Windows Vista
On a Windows Vista-based computer, you open a Visio diagram that contains a list. If the list contains multiple items, the items do not appear. - A primary key field of the BigInt type or of the TinyInt type is changed to the Int type when you reverse-engineer a table in a Database Model diagram
You use Microsoft Visio for Enterprise Architects to reverse-engineer a table in a Database Model diagram. If the table contains a primary key field of the BigInt type or of the TinyInt type, the key field type is changed to Int. - A long diagram name in a UML Model Diagram does not appear in the Model Explorer window
You create a sequence diagram in a UML Model Diagram. If you name the diagram page by using a name that contains more than 32 characters, the diagram name does not appear in the Model Explorer window. - Code in a large stored procedure may be truncated when you try to reverse-engineer a Database Model diagram
When you try to reverse-engineer a Database Model diagram that contains a large stored procedure, the code in the stored procedure may be truncated. - You receive a validation error message after you try to reverse-engineer a Database Model diagram that contains two tables that have the same index name
In Visio for Enterprise Architects, you have a Database Model diagram that contains two tables that have the same index name. If you try to reverse-engineer the Database Model diagram and then look for errors on the database model, you receive a validation error message. - You receive a validation error message after you try to reverse-engineer a Database Model diagram that contains a table that uses the BitColumn bit
In Visio for Enterprise Architects, you have a Database Model diagram that contains a table that uses the BitColumn bit. If you try to reverse-engineer the Database Model diagram and then look for errors on the database model, you receive a validation error message. - Underlines do not appear in the Text Editor window when you use the Japanese Input Method Editor (IME) in hiragana mode
Consider the following scenario. You run Visio 2003 on a Windows Vista-based computer. Additionally, you install the Japanese IME. When you switch the Japanese IME to hiragana mode, underlines do not appear in the Text Editor window. - An ActiveX control's toolbars do not appear when you start the control in Internet Explorer 7
You open a diagram that contains an ActiveX control in Internet Explorer 7. When you click to start the control, the control's toolbars do not appear. - Column descriptions are not imported for a table that uses a non-database object (DBO) schema
If you import a table that uses a non-DBO schema, the column descriptions are not imported. - The "CallThis" function that enables shapes to call Microsoft Visual Basic for Applications (VBA) functions does not work
You use ShapeSheet functions in Visio 2003. If you use the CallThis function to enable shapes to call VBA functions, the CallThis function does not work.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Additional query words: visio2003 visio2k3 visio11 vso2003 vso2k3 vso11
Keywords: kbtshoot kbfix kbupdate kbpubtypekc kbmsccsearch kbexpertisebeginner kbvisio2003sp3fix KB938794
