Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Export Bridge to Microsoft Office Visio Database Diagram (via ERX)

Bridge Specifications

Vendor Microsoft
Tool Name Office Visio Database Diagram
Tool Version 97 to 2016
Tool Web Site http://microsoft.com/visio
Supported Methodology [Data Modeling] Data Store (Physical Data Model, Logical Data Model) via erwin 3 (.ERX) File

SPECIFICATIONS
Tool: Microsoft / Office Visio Database Diagram version 97 to 2016 via erwin 3 (.ERX) File
See http://microsoft.com/visio
Metadata: [Data Modeling] Data Store (Physical Data Model, Logical Data Model)
Component: CaErwin35ErxExport.MicrosoftOfficeVisio version 11.2.0

OVERVIEW
REQUIREMENTS
n/a

FREQUENTLY ASKED QUESTIONS
n/a

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Generates a erwin ERX file.

In order to load the converted model in erwin:

1. Open the .erwin file in erwin.
2. Select File, then Save As...
3. Select 'XML Repository (*.XML)' for the 'Save as type' pulldown.
4. Specify a path and name for the exported file.
5. Click OK

In order to load the converted model into another Design Tool that supports the ERX format, please refer to the tool documentation.
FILE *.erx   Mandatory
Target database The target database. 'Auto Detect' will attempt to auto-detect the target database from the originating model. ENUMERATED
Auto Detect
AS/400 2
AS/400 3
AS/400 4.x
DB2/MVS 2
DB2/MVS 3
DB2/MVS 4
DB2/390 5
DB2/CS 2
DB2/UDB 5
Informix 4.x
Informix 5.x
Informix 7.x
Informix 9.x
Ingres 6.4
Ingres 1.x
Ingres 2.x
InterBase
Oracle 7.0
Oracle 7.1
Oracle 7.2
Oracle 7.3
Oracle 8.x
Progress 7.0
Progress 8.x
Rdb 4
Rdb 6
Rdb 7
Red Brick 3.0
Red Brick 4.0
Red Brick 5.x
SQL Server 4.x
SQL Server 6.x
SQL Server 7.x
SQLBase 5.0
SQLBase 6.x
Sybase 4.2
Sybase 10
Sybase 11.x
Teradata 1
Teradata 2.x
Watcom 3
Watcom 4
SQL Anywhere 5
Access 1.1
Access 2.0
Access 7
Access 97
Clipper
DBase 3
DBase 4
FoxPro
Paradox 4.x
Paradox 5.x
Paradox 7.x
HiRDB
ODBC 2.0
ODBC 3.0
SAS
Auto Detect  
Order Attributes on Primary Key position Order the attributes in the order of the Primary key. BOOLEAN   False  
Export dimensional properties Enables the dimensional modeling features for this model and exports the dimensional role (fact, dimension, outrigger) and dimensional type (fixed vs slowly changing) of the tables. BOOLEAN   False  
Encoding Select the character set encoding of the model to be imported. If there are multiple choices for a language, the actual encoding is indicated between parentheses. ENUMERATED
Central and Eastern European (ISO-8859-2)
Central and Eastern European (Windows-1250)
Chinese Traditional (Big5)
Chinese Simplified (GB18030)
Chinese Simplified (GB2312)
Cyrillic (ISO-8859-5)
Cyrillic (Windows-1251)
DOS (IBM-850)
Greek (ISO-8859-7)
Greek (Windows-1253)
Hebrew (ISO-8859-8)
Hebrew (Windows-1255)
Japanese (Shift_JIS)
Korean (KS_C_5601-1987)
Thai (TIS620)
Thai (Windows-874)
Turkish (ISO-8859-9)
Turkish (Windows-1254)
UTF 8 (UTF-8)
UTF 16 (UTF-16)
Western European (ISO-8859-1)
Western European (ISO-8859-15)
Western European (Windows-1252)
Locale encoding
No encoding conversion
   
Connection Allows selecting a connection by name, if the source model contains multiple database connections.
If the source model contains multiple connections and this parameter value is left empty, the connection with the most objects is selected.
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Fri, 23 Aug 2024 17:40:35

Copyright © 1997-2024 Meta Integration Technology, Inc. All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.