The current 10.2 release of ArcGIS Diagrammer does not work with ArcGIS Desktop 10.3 and will be the final Diagrammer release according to the link here.
ArcGIS Diagrmmer functionality is needed for ArcGIS Desktop 10.3.
Add a utility or tool to create, edit and analyze the geodatabase schema. The ArcGIS Diagrammer available from ArcScripts is an example of such a utility. Schema is presented as editable graphics in an environment familiar to users of Microsoft Visual Studio 2005. Essentially ArcGIS diagrammer is a visual editor for ESRI’s Xml Workspace Document which are created by ArcCatalog, the management application in the ArcGIS Desktop product suite.
Add the Geodatabase Designer from ArcScripts to ArcGIS. The Geodatabase Designer is set of tools to document and exchange geodatabase schema. GD2 also includes an editor for geometric network connectivity rules.
I agree that this is badly needed. In addition, the tool needs to also provide the ability to reapply schema to existing geodatabases. For instance, if I delete composite relationships and geometric networks in order to load data with the Simple Data Loader, I should be able to then reapply those relationships and networks after the data load.
Such an integrated tool will go a long way to make designing, documenting, and diagramming (the three Ds) in ArcGIS a lot smoother instead using other add-ins or third party tools which doesn't always work well.
"ArcGIS 9.3.1 was the last release to support CASE tools and the Import Schema Wizard functionality in the box. At ArcGIS 10 we will continue to allow users to use CASE functionality to design and implement geodatabase schema with Microsoft Visio and Rational Rose. This CASE functionality will be available as a separate setup that will be included in the media for ArcGIS 10 Final. This CASE functionality will be provided as an "Add‐On" to ArcCatalog, which will consist of the Schema Wizard and Semantics Checker. This CASE "ADD‐On" will be fully supported by ESRI Technical Support. Beyond ArcGIS 10, we continue to see a need for tools to diagram and define geodatabase schemas, and we will be looking at the best patterns and practices for supporting this in the future."
"ArcGIS 10.0 will be the last release of Microsoft Visual Basic for Applications (VBA); we will no longer support VBA beyond the ArcGIS 10.0 release. Microsoft no longer promotes or updates VBA. ESRI strongly recommends that no further development occur on this platform. Beyond ArcGIS 10.0, ESRI will no longer be able to support VBA as a development platform. Users who have custom functionality built using VBA should actively plan strategies to rewrite their applications using a supported development language such as Python, VB.NET, or C# so their applications continue to be operational and supported in future releases of ArcGIS."
"ArcGIS 9.3.1 was the last release supporting Microsoft Visual Basic 6 (VB6). Microsoft no longer supplies or supports VB6, and we can no longer support this development platform. Users who have custom functionality built using VB6 will need to rewrite their applications using a supported development language (e.g. VB.NET, C#) for their applications to be supported in 10.0."
This is a terrific idea. Without a CASE tool for geodatabase design, the geodatabase will never be accepted by the IT community as a legitimate "enterprise" database. It's extremely important that reverse engineering be incorporated into whatever CASE extension ESRI comes up with, as well as the ability to document the "delta" between a CASE tool model and an actual geodatabase.
The GDBT is a great set of tools. GBD Designer is an excellent choice for review and modification of the GDB. GDB Diagrammer provides a method for creating high quality stylized GDB documentation products that stand on thier own.
I agree with this! Especially because Geodatabase Designer no longer works with ArcGIS 10. A geometric network involving many feature classes can take a very long time to rebuild and reset connectivity rules if you have to remove it (like I do because of a data corruption). Without tools to manage geometric networks, implementing one often creates more problems and limitations than it does solutions.
