Microsoft KB Archive/259178

{|
 * width="100%"|

Visual Modeler 2.0 Common Support Issues (FAQ)

 * }

ID: Q259178

-

The information in this article applies to:


 * Microsoft Visual Basic Enterprise Edition for Windows, version 6.0

-

SUMMARY
Visual Modeler 2.0 is included with the Enterprise Edition of Microsoft Visual Studio 6.0 and with the Enterprise Editions of individual Visual Studio language products. This article summarizes the Visual Modeler 2.0 issues most frequently encountered by Microsoft Developer Support.

The Visual Modeler 2.0 documentation explains that:

&quot;Visual Modeler is a graphical object modeling tool that is tightly integrated with Microsoft Visual Studio 6.0. Visual Modeler allows you to fulfill the promise of object-oriented programming by quickly and easily creating applications that are maintainable, have a long lifetime, and are comprised of components that can be reused in other applications... Visual Modeler is a subset of the Rational Rose tool, both developed by Rational Software Corp.&quot;

The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

MORE INFORMATION
Following is a list of the Visual Modeler 2.0 issues most frequently encountered by Microsoft Developer Support. Some of these issues are addressed in separate articles in the Microsoft Knowledge Base, as noted:


 * 1) Visual Modeler is included only with the Enterprise editions of Visual Studio and with the Enterprise editions of individual Visual Studio language products, such as Visual Basic Enterprise Edition. Visual Modeler is not included in the Learning or Professional Editions of these products and cannot be purchased separately.

Users who require a modeling product can learn more about the full Rational Rose product at:

http://www.rational.com/products/rose/index.jtmpl

Users who require a modeling product may learn about the Microsoft Visio product line at the following Microsoft Web site:

http://www.microsoft.com/office/visio/default.htm
 * 1) Visual Modeler may crash with a General Protection Fault in KERNEL32 at random moments, such as when naming a class or changing the name of a class

Cause: Various trackball and mouse drivers.

Resolution: Use the Windows Task Manager, stop and remove running driver programs of this sort, and then retest Visual Modeler until the incompatible driver is identified.

Alternative resolution: Edit the ROSE.INI file and change the WordBreakProc setting from Yes to No.
 * 1) Visual Modeler only saves to the local Microsoft Visual SourceSafe database, although a shared remote database is in use. If you have installed Visual SourceSafe on the local machine, when you add a Visual Modeler model to the Visual SourceSafe database, you only see the project tree from the local database, although a shared database may be in use.

Resolution: Uninstall the local copy of Visual SourceSafe, and then install the client from the remote server by using netsetup.exe.
 * 1) The Visual Basic underscore line continuation character causes Visual Modeler to freeze during reverse engineering.
 * 2) Error message &quot;No Visual Basic Project was selected for reverse engineering&quot; during reverse engineering.
 * 3) The OrderSys example referenced in the Visual Modeler documentation is not installed.
 * 4) Add-ins, such as the Visual Modeler add-ins for Visual Basic, are generally available only to the user who installed Visual Studio.
 * 5) A report generation option available in Visual Modeler 1.0 is no longer on the version 2.0 menu, but can be added back manually.