MSJ Adminguide PDF

MicroStation/J®
Administrator’s Guide
DAA004470-1/0005
Trademarks
AccuDraw, Bentley, the "B" Bentley logo, MDL, MicroStation,
MicroStation/J, MicroStation MasterPiece, MicroStation Modeler,
MicroStation PowerDraft, MicroStation Review, MicroStation SE,
MicroStation Vault, PowerScope, QuickVision, SmartLine, and
TeamMate are registered trademarks; Bentley SELECT is a service
mark of Bentley Systems, Incorporated or Bentley Software, Inc.
Java™ and all Java-based trademarks and logos are trademarks

or registered trademarks of Sun Microsystems, Inc. in
the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, the Acrobat logo, Distiller, Exchange,
and PostScript are trademarks of Adobe Systems Incorporated.
Windows is a registered trademark of Microsoft® Corporation.
Other brands and product names are the trademarks of

their respective owners.
United States Patent Nos. 5,815,415 and 5,784,068.
Copyrights
©2000 Bentley Systems, Incorporated.
MicroStation ©1998-2000 Bentley Systems, Incorporated.
IGDS file formats ©1981-1988 Intergraph Corporation.
Intergraph Raster File Formats ©1993 Intergraph Corporation.
Portions ©1992-1994 Summit Software Company.
Portions ©1992-1997 Spotlight Graphics, Inc.
Portions ©1993-1995 Criterion Software Ltd. and its licensors.
Portions ©1992-1998 Sun MicroSystems, Inc.
Portions © Unigraphics Solutions, Inc.
Icc ©1991-1995 by AT&T, Christopher W. Fraser, and David
R. Hanson. All rights reserved.
Portions ©1997–1999 HMR, Inc. All rights reserved.
Portions ©1992–1997 STEP Tools, Inc.
Sentry Spelling-Checker Engine ©1993 Wintertree Software Inc.
Unpublished – rights reserved under the copyright laws of the
United States and other countries. All rights reserved.
MicroStation/J Administrator’s Guide

MicroStation/J Administrator’s Guide
Table of Contents
Part I: Workspaces
1. Workspace Fundamentals
Workspace Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Setting up the workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Locating the components of the workspace combo boxes . . . . . . . . . . . . . . . . . . . . . . 1–4
User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Project .............................................................................................................................. 1–4
Interface .......................................................................................................................... 1–5
Style ................................................................................................................................. 1–6
Creating your own user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Selecting workspace components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Supplied Sample Workspace Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
2. Sample Workspace Components

Summary of Sample Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Architectural Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Architectural seed files ....................................................................................................... 2–2
Architectural cell libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Architectural sample design files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Architectural custom line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Architectural level structure files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Architectural glossary file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Architectural settings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
AutoCAD Transition Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Civil Engineering Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Civil engineering seed files ............................................................................................... 2–10
Civil engineering cell library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Civil engineering design files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Civil engineering sample custom line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Civil engineering level structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Civil engineering glossary file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Civil engineering settings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
MicroStation/J Administrator’s Guide i

Table of Contents
Introductory Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15

Mapping Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Mapping seed files ............................................................................................................. 2–15
Mapping sample cell libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16
Mapping sample design files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Mapping tag sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–19
Mapping custom line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Mapping level structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Mapping glossary file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–22
Mapping settings file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–22
Mechanical Drafting Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–23
Mechanical drafting seed files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–23
Mechanical drafting cell libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–24
Mechanical drafting sample design files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–25
Mechanical drafting sample custom line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–27
Mechanical drafting level structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–28
Mechanical drafting glossary file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–29
Visualization project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–29
Visualization sample design files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–30
3. Workspace Configuration
Configuration Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
How MicroStation processes configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Determining configuration variable settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Levels of configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Types of configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
User Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Project Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
Working With Configuration Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7
General Procedure — To Modify User-level Configuration Variables . . . . . . . . . . . . . . . 3–7
User configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12
User Interface Modification Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–36
User Preference Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
Configuration Variable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
The Main Configuration Variable File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39
Configuration Variable File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–40
Variable definition references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–42
MicroStation-defined variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43
Preprocessor directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–43
Debugging Variable Definition Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–45
ii MicroStation/J Administrator’s Guide

Table of Contents
4. Customizing the User Interface

Tool Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
General Procedure — To customize “parent” tool frames . . . . . . . . . . . . . . . . . . . . . . . . 4–2
Rearranging child tool boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Inserting child tool boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
Expanding menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Rearranging tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
Inserting tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
Modifying tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
General Procedure — To Modify a Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
Pull-Down Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
General Procedure — To Customize the Main Menu Bar . . . . . . . . . . . . . . . . . . . . . . . 4–15
Rearranging menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Modifying menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
Inserting menus and menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–21
View Control Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
General Procedure — To Customize View Control Bars . . . . . . . . . . . . . . . . . . . . . . . . 4–23
User Interface Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
AccuDraw Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
Function Key Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
Digitizing Tablet Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
Types of digitizing tablet menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Attaching and activating tablet menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
Selecting menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–32
Deactivating menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33
Sample menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33
Customization terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
Customizing cursor button menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
Customizing command and matrix menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41
Tutorial execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41
Tutorial cell format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Tutorial text node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Control information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
Display information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43
Tutorial drawing conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43
MSTUT error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Action Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Action types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–48
Action type options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
Entering multiple action strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
MicroStation/J Administrator’s Guide iii

Table of Contents
Part II: Exchanging and Sharing Data
5. Exchanging Data with Other Applications

Design Data in Other File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Other Types of Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2
General Data Exchange Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Basic terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Choosing which translation to use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Preserving as much data as possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5
Opening a 3D file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Keeping units and measurements correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Using settings files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Versions supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
General Data Exchange Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Opening files in other formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Saving files in other formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12
IGES File Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
JAMA-IS IGES Translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
Import/Export IGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
Importing dimension elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
Exporting dimension elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
IGES entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15
IGES file organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Start section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16
Global data section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
Directory entry section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
Parameter data section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–17
Terminate section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
A sample design file and exported IGES file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18
Issues that affect IGES import and export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–19
Converting subfigure names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20
Converting text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21
Converting line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–23
Issues that affect IGES import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Keeping coordinate units correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–24
Drawing sheets and view visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–26
Issues that affect IGES export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–27
Excluding IGES entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–27
Alternate entities for excluded IGES entities (export) . . . . . . . . . . . . . . . . . . . . . . . 5–28
Exporting CALS-compliant IGES files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–29
iv MicroStation/J Administrator’s Guide

Table of Contents
Settings files for CALS export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30

IGES to MicroStation element conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–33
MicroStation to IGES element conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–38
IGES translation errors and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–39
Import and export errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Import errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–40
Export error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–41
Import and export warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–41
Import warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–42
Export warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–46
Available references about IGES ...................................................................................... 5–47
Parser/Verifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–47
STEP AP203/AP214 File Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–47
Importing STEP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–48
Exporting STEP data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–50
Boundary representation data exchange and healing . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
Notes regarding Step AP203/AP214 translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–52
VRML Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–53
Viewing VRML worlds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–54
VRML exporting and viewing hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–55
Screen Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–55
General Procedure — To Capture Part or All of a Screen . . . . . . . . . . . . . . . . . . . . . . . 5–56
Supported Image Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
MicroStation Field format (GRD) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–61
Setting the number of colors in exported images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Clipboard Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Copying to the Windows Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Pasting from the Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–63
Dynamic Data Exchange (DDE) links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–63
Pasting audio notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–65
Pasting animation sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–66
Sending views to other applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–67
General Procedure — To Serve a View Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Editing View Objects in Other Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–69
Updating view objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–70
Notes regarding view objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–71
OLE Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Linking and embedding objects in MicroStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–72
Editing and updating linked and embedded objects . . . . . . . . . . . . . . . . . . . . . . . . . 5–75
OLE Container configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–77
Notes regarding source application limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–78
Sending key-ins to MicroStation through a DDE link . . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
Sample DDE “conversation” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
Importing Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–81
MicroStation/J Administrator’s Guide v

Table of Contents
Using Redline Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–82
6. Building Custom Projects

Designing a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
Sample modules delivered with MicroStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Module design goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
Creation, maintenance, and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
File duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
Assembling Module Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
Seed Design Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
General Procedure — To create a seed file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
Cell Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Using multiple cell libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
Dimension-driven Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Important terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
Diagnosing an ambiguous dimension-driven cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
Equation syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
Algebraic expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12
White space and comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–13
Arithmetic operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–13
Built-in numerical constants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
Variable names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–14
DD Design tool frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
Profile tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
Sketch Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
Convert Element to Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22
Parameter Constraints tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23
Convert Dimension to Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24
Assign Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
Assign Variable to Dimensional Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26
Attach Element tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–27
Construct Attached Line String or Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
Construct Attached Arc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–29
Construct Attached Ellipse or Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–29
Attach Element to Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–30
Align Element with Point and Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–30
Attach Pen Element to Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–31
Geometric Constraints tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–32
Constrain Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–33
vi MicroStation/J Administrator’s Guide

Table of Contents
Make Construction or Parameter Invariant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38

Constrain Point On Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
Constrain Point at Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–39
Constrain Two Points to be Coincident . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–40
Fix Point at Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–41
Equate Parameters or Constructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–41
Evaluate Constraints tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–42
Re-solve Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–43
Modify and Re-solve Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–45
Describe Selected Construction or Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–46
Modify Constraint tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–47
Break Constrained Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–48
Trim Constrained Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–49
Fillet Constrained Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–49
Chamfer Constrained Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–51
Modify Value of Dimension or Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–53
Dimension-Driven Design dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54
Level Structure Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–55
Guidelines for creating a level structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–55
General Procedure — To create a level structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–56
Color Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–61
Balanced colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–61
General Procedure — To customize a color table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–62
Line Style Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–65
Copying Line Style Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–65
Line style components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–67
Stroke pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–67
Point symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–68
Compound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–69
General Procedure — To define a line style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–69
Working with stroke pattern components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–71
Working with point symbol components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76
Working with compound components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–81
Technical background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–83
Settings Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84
Creating settings files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–85
General Procedure — To create a settings group “from scratch” . . . . . . . . . . . . . . . . . . 6–86
General Procedure — To define a drawing component . . . . . . . . . . . . . . . . . . . . . . . . . 6–88
Cell scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92
Defining dimension and multi-line styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–93
Modifying the Project Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
Archiving: Bundling Module Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–97
Overview of the Archive utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–97
Selecting the resources to be archived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–98
MicroStation/J Administrator’s Guide vii

Table of Contents
The archive process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–99

The extraction process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–99
Creating and manipulating archive files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–100
General Procedure — To use the Archive utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–100
Digital Signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
Typical uses of digital signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–106
General Procedure — To digitally sign files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–107
Key pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–107
Keeping the private key private . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–108
Signing Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–109
Verifying Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–110
Updating files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–110
Algorithms used for digital signatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–112
Other aspects of the Archive utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–112
Working with Windows Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–112
Working with your own resource classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–113
Part III: Internet Technologies
7. Engineering Links
Engineering Links tool box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
Show Engineering Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2
Attach Engineering Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
Follow Engineering Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Connect to/Disconnect from Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
Load RefAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
Remote Open/Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
Entering the URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8
8. Publishing Data to the Internet

Using HTML Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
viii MicroStation/J Administrator’s Guide

Table of Contents
Part IV: Using Software Extensions
9. Scripts, Macros, and User Commands

Key-in Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Running macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2
User Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
Indexed UCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
General Procedure — To edit UCM index files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
10. MDL Applications

Loading and Unloading MDL Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Loading MDL Applications Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
Part V: External Database Interface
11. MicroStation and Non-graphical Data

Associating Elements to Non-graphical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
Tag to Database Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
What is the Database Interface? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
Why Use the Database Interface? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–3
What is a Relational Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
Why Use a Relational Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
Choosing a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
Selection Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–6
Database Product Families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–7
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–7
Product descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–8
Sybase database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–9
ODBC Database Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–10
RIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11
RIS tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–12
MicroStation/J Administrator’s Guide ix

Table of Contents
12. Connecting to Databases

Setting Up the Database Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
Connecting to ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
Accessing multiple DBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
dBASE notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Microsoft — SQL Server notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Connecting to Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
General Procedure — Setting Up Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
Windows Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
Connecting to Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
Connecting to RIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–10
General Procedure — Setting Up RIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
MS_LINKTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
Copying elements with attached linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
13. Linking Database Rows to Elements

Database Tools Available in MicroStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Visual SQL Query Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Visual SQL Query Builder dialog box overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–2
Building simple SELECT statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
Joining tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
Reviewing database attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Database form dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14
Locating linked elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–17
Opening, editing and saving form dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–18
Using SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–22
SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–22
SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
INSERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–23
CREATE TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
CREATE DATABASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
COMMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
ROLLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
Specific SQL Window key-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
DISCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
RELOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
Using the SQL Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–25
x MicroStation/J Administrator’s Guide

Table of Contents
Command files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–27

Manually committing SQL statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–28
Creating Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29
mslink column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
Key index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
MSCATALOG Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–31
mscatalog structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–31
tablename column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–32
entitynum column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–32
screenform column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
reporttable column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
sqlreview column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
fencefilter column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
dastable column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–34
formtable column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–34
Creating and maintaining MSCATALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–35
Database Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–38
Creating Linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–39
Defining the Active Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–39
Editing the Active Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–41
Setting Linkage Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–41
New linkage mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–42
Duplicate linkage mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–42
Information linkage mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–42
Attaching linkages to cell libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–43
Oracle Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–43
Editing the Active Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–43
RIS Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–43
nextocc MSCATALOG column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–44
14. Querying and Maintaining the Database

Reviewing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1
Setting attribute review selection criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1
Displaying Database Attributes in the Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–2
General Procedure — Displaying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3
Detaching Linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4
Detaching linkages from cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4
Verifying Linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5
Using the Database Verification utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–6
Manipulating elements with orphan linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–8
Manipulating linkages individually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–9
MicroStation/J Administrator’s Guide xi

Table of Contents
15. Generating Reports

Report Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–2
Fence Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–3
Report Formatting and Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–4
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–5
16. Database Application Software

Existing Database Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1
Developing MDL Database Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2
xii MicroStation/J Administrator’s Guide

Part I: Workspaces
Workspace Fundamentals
This chapter explains the concept of workspaces.
• The sample workspaces are covered in Sample Workspace

Components (see page 2-1) .
• The parts of a workspace and basic procedures for selecting them

are covered in Workspace Components (see page 1-1) .
• The nature of the sample workspaces delivered

MicroStation is covered in Supplied Sample Workspace
Components (see page 1-11) .
A workspace is a custom MicroStation “environment” or configuration.

By selecting a workspace, you customize MicroStation for a
specific discipline, project, or task.
For example, MicroStation is delivered with a sample “architecture”

workspace. When the architecture workspace is active, the
files and tools you need to perform architectural designing and
drafting are available by default. In addition, the tools and
tool boxes that are unrelated to that discipline are “removed”
from the interface to avoid confusion.
You can also create your own MicroStation environments

and save them as workspaces.
Workspace Components
Workspace components are stored in Bentley’s “Workspace” and
“Home” directories. The following is a list of workspace components:
1 . User — This component in effect points to the active
workspace’s Project and Interface components. The user
name identifies the user configuration file (.ucf) in Bentley’s
“Workspace\users” directory.
MicroStation/J Administrator’s Guide 1–1

Setting up the workspace
2 . Project — A project consists of customized data files, such as

cell libraries and line style libraries, identified by configuration
variables in the project configuration file. The data files
in the sample projects provided with MicroStation are
delivered as modules, subdirectory trees under Bentley’s “
Workspace\projects\examples” directory.
3 . Interface — A customized user interface (defined in

modification resource files in subdirectories under Bentley’s
“Workspace\interfaces\MicroStation” directory).
4 . Style — MicroStation either opens a Status Bar or a Command

Window.
5 . (User) Preferences — Customized user preferences defined

in a user preference resource file (“<user_name>.upf”) in
Bentley’s “Home\prefs” directory.
You can select any available project, user interface, and style as
the components of the active workspace. The active workspace
components are identified by the user configuration file.
The name of the user configuration file is used as the name of

the workspace. Its suffix is “.ucf,” and it is stored in Bentley’s
“Workspace\users” directory. (The user preference files replace the
“userpref.rsc” file used by MicroStation Version 4.)

Workspaces are set up in MicroStation Manager. The MicroStation
Manager dialog box has combo boxes which allow you to select a
specific User, Project, and Interface. There is also a Style option
menu which allows you to select the Status Bar or Command
Window before entering a design file session.
1–2 MicroStation/J Administrator’s Guide

MicroStation
Manager
dialog box
The following chart cross references the 5.0 functions

associated with each combo box.
Combo box Equivalent to Version 5.0 action

User Selecting User menu > Workspace >
Select Default Workspace
Project Selecting User menu > Workspace >
Select Components and further selecting
the Project Components Select option.
Interface Selecting User menu > Workspace >
Select Components and further selecting
the User Interface Select option.
Locating the components of the workspace combo boxes
All of the options shown on the User, Interface, and Project combo
boxes are controlled by the contents of specific subdirectories located
under Bentley’s “Workspace” directory. By default, the following
filenames control what you see on these menus:

Combo box Files associated with the

combo boxes
User ".\projects\users\*.ucf"
Project ".\projects\*.pcf"
".\projects\examples\*.pcf"
".\projects\tutorials\*.pcf"
".\projects\untitled\*.pcf"
Interface “.\interfaces\MicroStation\” (list
of subdirectories)
User
The User combo box sets the path for saving and loading an
environment or configuration for later design file sessions.
Selecting a user from the list reconfigures MicroStation to
use that workspace’s components. Selecting a user also resets
the search path to a corresponding subdirectory for loading
design files. For example, selecting the “tutorials” user changes
the directory tree to “\projects\tutorials\intro\dgn” and
lists the design files in that location.
User combo box
A workspace can contain only one project and one interface. These
components are attached to a workspace. So, to use two different
projects with the same interface or two interfaces for one project,
you would need to make additional workspaces.
Project
A project is one component that can be associated with any
workspace. It is used to set the location and names of data files
associated with a specific design project.

Project combo
box
Interface
Another component of the workspace, the Interface combo box allows
you to select a specific look and feel of MicroStation’s tools and general
on-screen operation. In addition to the default interface, additional
sample interfaces are delivered with MicroStation.
Interface combo
box
Interface: autocad
This option provides AutoCAD command and tool names next to
corresponding MicroStation commands and tools.
Interface: newuser
This option provides a subset of the default graphical interface
to aid the new MicroStation user.
Interface: mde
This option provides graphical access to JMDL development tools.

Style
The Style option menu allows you to select either the older Command
Window method of communicating with MicroStation or the
standard Status bar. Whichever style you select, MicroStation
remembers it from session to session.
Style option
menu
Creating your own user interface

In addition to activating an existing interface, the Interface combo box
can also be used to create an entirely new interface. Choosing New from
the Interface combo box brings up the Create User Interface dialog box.
Create User
Interface dialog
box
After entering a name and description for your new interface,

MicroStation creates an interface directory under the
“Workspace\interfaces\MicroStation” subdirectory. This new interface
uses the default interface as its starting point. Any changes you make
while using this new interface will be written only to the new interface.
Selecting workspace components

When the workspace user is changed in the MicroStation
Manager dialog box, the active workspace’s project component
is automatically changed.

Do not delete the “examples” files and directories. If you

do delete them, use the MicroStation installer to reinstall
them (with a custom installation).
To change the workspace user

1. From the User combo box in the MicroStation Manager
dialog box, choose the desired user.
The project associated with that user is automatically chosen.
MicroStation
Manager
dialog box
with the User
combo box
displayed
To change to a different project

1. From the Project combo box in the MicroStation Manager
dialog box, choose the desired project.

To change to a different interface

1. From the Interface combo box in the MicroStation Manager
dialog box, choose the desired interface.
To create a user configuration file

1. From the User combo box in the MicroStation Manager
dialog box, choose New.
The Create User Configuration File dialog box opens.
Create User
Configuration
File dialog
box
2. In the Create User Configuration File dialog box, type the name
of the new workspace (the name for the new user configuration
file). The suffix “.ucf” is automatically added to the name.
3. Click OK.
A second Create User Configuration File dialog box opens.
Create User
Configuration
File dialog
box, after
giving the file
a name

4. (Optional) — In the Create User Configuration File dialog

box’s Description field, enter a workspace description of
up to 32 characters in length.
5. (Optional) — Select additional workspace components. See To

select a new workspace’s project component on page 1-9 and To
select a new workspace’s user interface component on page 1-10.
6. Click OK.
The user configuration file is saved and is automatically chosen in
the User combo box in the MicroStation Manager dialog box.
To select a new workspace’s project component

1. In the (second) Create User Configuration File dialog box,
click the Project: Select button.
The Select Project Configuration File dialog box opens. The
available project configuration files are displayed in the list box.
2. Select a project and click OK.

To select a new workspace’s user interface

component
1. In the (second) Create User Configuration File dialog box,
click the User Interface: Select button.
The User Interface dialog box opens. The available user
interfaces display in the list box.
User
Interface
dialog box
2. Select a user interface and click OK.
To create a new project component

1. From the Project combo box in the MicroStation Manager
dialog box, choose New.
The Create New Project dialog box opens.
Create New
Project dialog
box
2. In the Name field, key in the name of the new project. The
name may be up to 32 characters in length.

Supplied Sample Workspace Components
3. (Optional) — In the Description field, enter a project description

of up to 32 characters in length.
4. Click OK.
The project configuration directory is created, and the
project is automatically chosen in the MicroStation Manager
dialog box’s Project combo box.
To create a new user interface component

1. From the Interface combo box in the MicroStation
Manager dialog box, choose New.
The Create User Interface dialog box opens.
Create User
Interface
dialog box
2. In the Name field, key in the name of the new interface. The
name may be up to 32 characters in length. The list box
displays the names of existing interfaces.
3. (Optional) — In the Description field, enter a workspace
description of up to 32 characters in length.
4. Click OK.
The interface directory is created, and the interface is
automatically chosen in the MicroStation Manager dialog
box’s Interface combo box.

Sample project, user interface, and user preference components
are supplied with MicroStation.

• Each sample project component has its own subdirectory

tree, within Bentley’s “Workspace\projects” directory tree,
that contains subdirectories for design files, seed files, cell
libraries, symbology resources, and so on.
• Each sample interface component has its own subdirectory in
Bentley’s “Workspace\interfaces” directory.
This makes it easy to maintain and customize projects.
For more information about the sample workspace components,

see Sample Workspace Components on page 2-1. For more
information about customizing workspace components, see
Building Custom Projects on page 6-1, Customizing the User
Interface on page 4-1, and Setting User Preferences in the User
Preferences chapter of the on-line User’s Guide.

Sample Workspace
Components
Sample workspace components are provided with MicroStation to
demonstrate the types of components you can include in workspaces
and how you can structure the workspaces you create for your own
projects. You may even find that some of the sample workspace
components are useful without any modification.
Summary of Sample Components

This table lists the workspace components provided.
Preferences User interfaces Projects

Default Default Architectural
AutoCAD AutoCAD Civil Engineering
Transition Transition
Introductory
Mechanical
Drafting
Working Directory
You can combine any project with any user interface and set
of preferences to create a workspace. For instructions, see
Workspace Components on page 1-1.
For information about creating your own components, see:
• Setting User Preferences in the User Preferences chapter

of the on-line User’s Guide
• Customizing the User Interface (see page 4-1)
• Building Custom Projects (see page 6-1)

Sample Workspace Components
Architectural Project
Architectural Project
The Architectural project component includes sample architectural
design files, seed files, cell libraries, border files, custom
line styles, as well as a named level structure, glossary,
function key menu, and more. These files are in Bentley’s
“Workspace\projects\examples\arch” directory.
Architectural seed files

The default seed file in the Architectural project, “archseed.dgn,”
is provided as a basis for architectural design.
Filename Description
"archseed.dgn" 2D architectural seed file with settings
commonly used by architects, such
as readouts in feet and inches,
fractions, level structures, cell and
style libraries, and menus.
"sdarch2d.dgn " 2D and 3D architectural seed files
"sdarch3d.dgn " historically supplied with MicroStation.
"sdarch.sht" Architectural seed sheet file with
settings commonly used by architects.
"sdarchah.sht" Architectural seed sheet files for A-size
"sdarchav.sht" drawings — horizontal and vertical
orientation, respectively.
"sdarchb.sht" Architectural seed sheet files for B-,
"sdarchc.sht" C-, D-, E-, and F-size drawings.
"sdarchd.sht"
"sdarche.sht"
"sdarchf.sht"
Architectural cell libraries

These 2D cell libraries are supplied for architects. Most cells have
fixed sizes, but some enable you to determine the size and scale. These

Architectural cell libraries
cells are stored at 1" size. Doors, windows, columns, shower stalls,
lights, and vents are designed to be placed using this method.
Architectural
cell library
"arch.cel"
"arch.cel " Cell library with commonly used
architectural symbols. The cells in this
library were created by Technicon, Idea
Graphix, and Intergraph Corporation.
"archpat.cel " Cell library containing commonly used
linear and area pattern cells.
Architectural
pattern
cell library
"archpat.cel"

Architectural sample design files

These sample architectural design files are supplied:
"building.dgn" 3D model of hi-rise building in
urban setting.
"ddarch.dgn" Sample dimension-driven designs. Can
be placed as dimension-driven cells.
"igi_flrp.dgn" Sample house floor plan developed
by IdeaGraphix, Inc.
"igi_hous.dgn" Sample composite house floor plan sheet

developed by IdeaGraphix, Inc.
"igi_land.dgn" Sample house landscape plan developed
by IdeaGraphix, Inc.
"lad_dia.dgn " Sample partial concept model for the
National Science Center. Courtesy,
Leo A. Daly.
"lad_ele.dgn" Sample partial concept model for the
Leo A. Daly.
"lad_eln.dgn" Sample partial concept model for the
Leo A. Daly.
"lad_els.dgn" Sample partial concept model for the
Leo A. Daly.
"lad_elw.dgn" Sample partial concept model for the
Leo A. Daly.
"lad_modl.dgn " Sample composite concept model
for the National Science Center.
Courtesy, Leo A. Daly.
"lad_pavp.dgn" Sample partial concept model for the
Leo A. Daly.

"lad_roof.dgn" Sample partial concept model for the
Leo A. Daly.
"lad_towr.dgn" Sample partial concept model for the
Leo A. Daly.
"lindal.dgn" House floor plan, courtesy of Lindal
Cedar Homes.
"liv_room.dgn" Interior of residence.
"pool.dgn" Indoor swimming pool.
"sc_fp.dgn" Sample floor plan developed by

Steelcase, Inc.
"sc_rc.dgn" Sample reflected ceiling plan developed
by Steelcase, Inc.
"sc_sp.dgn" Sample space plan developed by
Steelcase, Inc.
The floor plan below shows a typical file from the list of supplied designs:
Sample
design file
"sc_fp.dgn"
These sample architectural border design files are attached as

reference files to many of the architectural sample design files.

Architectural custom line styles
"border_d.dgn" D size at 1/8" scale
"border_e.dgn" E size at 1/8" scale
"border_f.dgn" F size at 1/8" scale
"border_g.dgn" G size at 1/8" scale
"border_h.dgn" H size at 1/8" scale

The "archlsty.rsc" line style library has these sample line styles:
Line Style Description

Name
Batt Batten Insulation
Break Line Line break
Fire - 1HR One Hour fire rated walls.
Fire - 2HR Two Hour fire rated walls.
Fire - 3HR Three Hour fire rated walls.
Fire - 4HR Four Hour fire rated walls.
Smoke - 1HR One Hour smoke partitions.
The "heatlsty.rsc" line style library has these sample line styles:

Name
Compressed Compressed Air
Air
Feedwater Feedwater Discharge
Discharge
Fuel Oil Return Fuel Oil Return
Fuel Oil Fuel Oil Suction
Suction


Name
Fuel Oil Vent Fuel Oil Vent
High Pressure High Pressure Return
Return
High Pressure High Pressure Supply
Supp
Hot Water Ret Hot Water Return
Hot Water Sup Hot Water Supply
Low Pressure Low Pressure Return
Ret
Low Pressure Low Pressure Steam
Steam
Vacuum Pump Vacuum Pump Discharge
Discharger
The "hvaclsty.rsc" line style library has these sample line styles:

Name
Chill Water Chilled Water Return
Return
Chill Water Chilled Water Supply
Supply
Cond. Water Condenser Water Return
Return
Cond. Water Condenser Water Supply
Supply
Drain Drain
Humidification Humidification
The "plmblsty.rsc" line style library has these sample line styles:


Name
Argon Argon
Cold Water Cold Water Return
Return
Cold Water Cold Water Supply
Supply
Comb Combination Standpipe
Standpipe
Compressed Compressed Air
Air
Drink Water Drinking Water Return
Return
Drink Water Drinking Water Supply
Supply
Dry Standpipe Standpipe - Dry
Helium Helium Gas
Hot Water Hot Water Return
Return
Hot Water Hot Water Supply
Supply
Hydrogen Hydrogen Gas
Liquid Liquid Petroleum Gas
Petroleum Gas
Liquid Liquid Nitrogen
Nitrogen
Liquid Oxygen Liquid Oxygen
Nitrogen Nitrogen Gas
Nitrous Oxide Nitrous Oxide Gas
Oxygen Oxygen
Storm Drain Storm Drain
Vacuum Vacuum

Architectural level structure files

Name
Vacuum Vacuum Cleaning
Cleaning
Wet Standpipe Standpipe - Wet
Architectural level structure files

A variety of level structure files are supplied, including several based
on standards defined the American Institute of Architects (AIA).
Architectural glossary file

The glossary file "arch.gls" has examples of commonly
used architectural terms and abbreviations. There are
too many entries to list here.
Architectural settings file

This settings file is supplied for architectural applications.
"archset.stg" Provides access to the project’s cells,
dimension styles, and multi-line styles.
AutoCAD Transition Interface

The AutoCAD Transition user interface differs from the default
interface in that in parentheses to the right of many menu items and the
tool tips are the equivalent AutoCAD terms. For example, to the right
of Cells in the Element menu is the equivalent AutoCAD term, Blocks.

Civil Engineering Project
For more information about making the transition from AutoCAD to

MicroStation, see AutoCAD Transition in the on-line help.
Civil Engineering Project

The Civil Engineering project is based upon available government
standards and public-domain symbology. It is intended for use with
civil/site applications by engineers and designers who regularly
prepare engineering layouts for plans and reports. These files are in
Bentley’s “Workspace\projects\examples\civil” directory.
Civil engineering seed files

These seed files are supplied for civil engineering applications.
"civ2d.dgn" 2D; working units of 1:100:10; origin
at back left x,y — intended for use
in site layout work.
"civ3d.dgn" 3D; working units of 1:100:10; origin at
center “Z” and back left x,y — intended
for use in site modeling work.
Civil engineering cell library

These cell libraries are supplied for civil engineering applications:

Civil engineering cell library
"civil.cel" cell
library
"civil.cel" Has cells for civil engineering layout and
detail work.
"civeng.cel" Has cells used with electronic field books.
(English version)
"civmet.cel" Has cells used with electronic field books.
(metric version)
"civeng.cel"
cell library

Civil engineering design files
"civmet.cel"
cell library
Civil engineering design files

These sample civil engineering design files are supplied:
"cogo.dgn" Coordinate geometry
"design.dgn" Proposed design
"dtm.dgn" Dimension-driven section
"profiles.dgn" Profiles
"pr_xs.dgn" Proposed cross-sections
"survey.dgn" Field survey data
"tables.dgn" Quantity tables
"terra.dgn" Rural landscape
"vert.dgn" Vertical alignments
Civil engineering sample custom line styles

The "civlsty.rsc" line style library has these line styles:

Civil engineering level structure

Cable/Tele- Indicates presence of
phone buried cable.
Concrete Concrete.
Parallel Lines Parallel lines along
curves, etc.
RC Pipe Left A precast section of
reinforced concrete pipe
(seams left)
RC Pipe Right A precast section of
reinforced concrete pipe
(seams right)
Rebar Concrete rebar.
Civil engineering level structure

The civil engineering sample level structure "civil.lvl" is as follows:
Num- Name Description

ber Group
1 C-PROP Property lines, survey :cbuild
benchmarks
2 C-TOPO Proposed contour lines :cbuild
and elevations
3 C-BLDG Proposed building footprints :cbuild
4 C-PKNG Parking lots :cbuild
5 C-ROAD Roads :cbuild
6 C-STRM Storm drainage catch basins :cbuild
7 C-COMM Site communication/tele- :cbuild
phone
8 C-WATR Dom. water-manholes, :cbuild
pump stations
9 C-FIRE Fire protection hydrants :cbuild

Civil engineering glossary file
Num- Name Description

ber Group
10 C-NGAS Natural gas manholes, :cbuild
meters, tanks
11 C-SSWR Sanitary sewer-manholes, :cbuild
pump stations
12 C-ELEV Elevations :cbuild
13 C-SECT Sections :cbuild
14 C-DETL Details :cbuild
15 C-SHBD Sheet border and title :cdraw
block lines
16 C-PSIT Site plan :cdraw
17 C-PELC Site electrical systems plan :cdraw
18 C-PUTL Site utility plan :cdraw
19 C-PGRD Grading plan :cdraw
20 C-PPAV Paving plan :cdraw
21 C-P*** Other site or civil plans :cdraw
22 C-ELEV Elevations :cdraw
23 C-SECT Sections :cdraw
24 C-DETL Details :cdraw
25 C-SCHD Schedules and title block :cdraw
sheets
Civil engineering glossary file

The glossary file "civil.gls" has examples of commonly used
civil engineering terms and abbreviations. There are too
many entries to list here.

Civil engineering settings file
Civil engineering settings file

This settings file is supplied for civil engineering applications.
"civset.stg" Provides access to the project’s area
patterns and cells.
Introductory Project
The Introductory sample project component consists of design files
necessary for working through the tutorials in the Tutorial Workbook.
This project is automatically activated when the workspace User is set
to tutorials in the MicroStation Manager dialog box. The project files
are in Bentley’s “Workspace\projects\tutorials\intro” directory.
Mapping Project
The Mapping project component includes sample mapping design files,
sample seed files, cell libraries, border files, and line style definitions,
a glossary, and level structure for mapping applications. These files
are in Bentley’s “Workspace\projects\examples\mapping” directory.
Mapping seed files

These seed files are supplied for mapping. The default seed file
for mapping applications is "map2d.dgn".
Seed File Description

"map2d.dgn" Basic 2D mapping seed file — working units of
1 FT:10:100 pu allows precision of 0.001 feet in
a design plane approximately 813 miles square.
"map3d.dgn" Basic 3D mapping seed file — uses same
working units as "map2d.dgn" with
additional settings for 3D.

Mapping sample cell libraries
Seed File Description

"sdmap2d.dgn" 2D and 3D mapping seed files (English units)
"sdmap3d.dgn" delivered with previous versions of MicroStation.
"sdmapm2d.dgn" 2D and 3D mapping seed files (metric units)

"sdmapm3d.dgn" delivered with previous versions of MicroStation.
Mapping sample cell libraries

These mapping cell libraries are supplied. Most cells are sized
for 1”=100’ scale mapping at an Active Scale of 1.
"mapping.cel"
"mapping.cel" Samples of map border cells.
"control.cel" Samples of survey and mapping control cells.
"land.cel" Samples of landbase cells.
"mappat.cel" Samples of patterning cells.
"control.cel"

Mapping sample design files
"land.cel"
"mappat.cel"

These sample mapping design files are supplied.

"maputil.dgn"
"contour.dgn" Sample contour map.
"mapland.dgn" Sample land map that demonstrates the use

of MicroStation for municipal mapping — has
both cadastral and planimetric features such
as road right-of-ways with their corresponding
centerlines, parcel information, buildings,
lakes and rivers. Tag sets are defined for
attaching non-graphical attributes (see
Mapping tag sets on page 2-19).
"maputil.dgn" Sample utility map that demonstrates the
use of MicroStation for utility mapping—
has electric cables, poles, street lights,
transformers and more. Tag sets are defined
for attaching non-graphical attributes (see
Mapping tag sets on page 2-19).

Mapping tag sets
"mapcont.dgn" Sample contour map that demonstrates the use
of MicroStation for topographic mapping —
has index, intermediate, hidden and depressed
contours and spot elevations, as well as examples
of horizontal and vertical control points.
"mapbord.dgn" A sample border file.
Mapping tag sets

The following tag sets are defined in "mapland.dgn" and " maputil.dgn".
Land Tag Set Tag Names

building address, name
centerline street name, alternate street
name, type
parcel parcel number
Utility Tag Tag Names

Set
cable size, material, length, phase,
voltage, circuit
conduit size, material
device type
fuse status, type, amp
manhole type, number
pedestal type
pole height, number, owner, class
switch status, type, number
transformer size, phase connect

Mapping custom line styles
Mapping custom line styles

The mapping line style library, "maplsty.rsc", has these line styles:
Line Style Name Description

Fence - Barbed Barbed Wire Fence
Fence - Chain Chain Link Fence
Link
Fence - Res Residential Boundary
Barbed Barbed Wire
Fence - Res Chain Residential Boundary
Chain Link
Guard Rail Guardrail
Parallel Lines Parallel lines along curve, etc.
RR - Abandoned Abandoned Railroad
RR - Single Active Railroad - Single
Site Drainage Site Drainage
Stream Natural Stream / Water
Source
Tree Line Tree Mass
Mapping level structure

The mapping level structure "mapping.lvl" is as follows:
Control Group — All Control Features

1 Horizontal — Horizontal Control
2 Vertical — Vertical Control
Land Group
10 Pavement — Edge of Pavement
11 Drive — Paved and Unpaved
Building Sub-Group

Mapping level structure
12 Building — All buildings

13 Address
14 Sidewalk
15 Parking — Parking Areas
16 Fence — Fence and Guardrails
17 Vegetation — Wooded areas and single trees
18 Water — Streams, creeks, rivers, ponds, and ditches
19 Bridges — Road and Railroad
20 Signs — Single, Double, and Overhead
21 Walls — Retaining and Sea
22 Cad Pole — Traffic, Street Light, Power, Tower
Cadastral Group
Parcel Sub-Group
30 Parcel
31 Parcel Text
Centerline Sub-Group
32 Centerlines — Street Centerline
33 Street Name — Street Centerline
Names
34 ROW — Street Right of Way Lines
Contour Group — All Contour Data
Index Sub-Group
40 Index — Index Contours
41 Index Text — Index Contour Text
42 Intermediate — Intermediate Contours
43 Spot — Spot Elevations
Electric Group — Electric Distribution Features
Cable Sub-Group
50 Cable — Overhead and
Underground

Mapping glossary file
51 Cable_Text
XFMR Sub-Group
52 XFMR — Transformer
53 XFMR Text
Switch Sub-Group
54 Switch
55 Switch Text
Pole Sub-Group
56 Pole — Utility Pole
57 Pole Text — Utility Pole Text
Fuse Sub-
Group
58 Fuse
59 Fuse Text
60 Pedestal
Mapping glossary file

The glossary file "mapping.gls" has examples of commonly
used mapping terms and abbreviations. There are too
many entries to list here.
Mapping settings file

This settings file is supplied for mapping applications.
"mapset.stg " Provides access to the project’s
Linear drawing settings group
components and cells.

Mechanical Drafting Project
Mechanical Drafting Project

The Mechanical Drafting sample project component includes
the data described here.
Mechanical drafting seed files

These seed files are supplied for mechanical drafting applications.
The default seed file is "mechdet.dgn".
"mechdet.dgn" For use in creating detail drawings.
"mechdetm.dgn" For use in creating detail drawings

with SI units.
"mechlay.dgn " For use in creating layout or
assembly drawings.
"mechlaym.dgn" For use in creating layout or assembly
drawings with SI units.
"sdmech2d.dgn" 2D and 3D mechanical seed files
"sdmech3d.dgn" (English units) historically supplied
with MicroStation.
"sdmeng2d.dgn " 2D and 3D mechanical seed files
"sdmeng3d.dgn " (metric units) historically supplied
with MicroStation.
"sdmech.sht" Mechanical seed sheet file with settings
commonly used by architects.
"sdmechah.sht" Mechanical seed sheet files for A-size
"sdmechav.sht" drawings — horizontal and vertical
orientation, respectively.
"sdmechb.sht" Mechanical seed sheet files for B-, C-,
"sdmechc.sht" D-, E-, and F-size drawings.
"sdmechd.sht"
"sdmeche.sht"
"sdmechf.sht"

Mechanical drafting cell libraries
Mechanical drafting cell libraries

These cell libraries are supplied for mechanical drafting applications.
Over 200 cells are included in the libraries listed below.
"weld.cel"
"geo.cel"
"finish.cel"

Mechanical drafting sample design files
"draft.cel"
"mechpat.cel" ANSI material patterns.
"weld.cel" Welding symbols.
"crosshd.cel" Phillips screw head, side and top view.
"geo.cel" Geometric Tolerancing symbols.
"finish.cel" Finish symbols.
"draft.cel" General drafting symbols.
"hexhd.cel" Hex head bolt heads, side and top views.
"slothd.cel" Slotted screw heads, side and top views.
"hexcaphd.cel" Hex slotted cap screw heads, side and top views.
"washers.cel" Flat washers, side and top views.
"nuts.cel" General nuts, side and top views.

This table lists the sample border design files supplied with the
Mechanical Drafting project. They are attached as reference
files to many of the sample design files.
"a0form.dgn" SI Project Border - 84.1 × 118.9

"ahform.dgn" Project Border - 8.5 × 11 (Landscape)
"avform.dgn" Project Border - 8.5 × 11 (Portrait)
"bform.dgn" Project Border - 11 × 17
"borda0.dgn " Project Border - A0.
"cform.dgn" Project Border - 17 × 22
"dform.dgn" Project Border - 22 × 34
"eform.dgn" Project Border - 34 × 44

This table lists the sample design files supplied with the
Mechanical Drafting project.
"countwt.dgn" Counter weight design created by
Duo-Fast Corporation.
"engine.dgn" Dimension-driven model of an internal
combustion engine.
"gear.dgn" Gear design created by Intergraph
Corporation.
"pulley.dgn" Pulley design created by Duo-Fast
Corporation.
"rim.dgn" Rim design created by Intergraph
Corporation.
"shaft.dgn " Shaft design created by Duo-Fast
Corporation.
"spindle.dgn" Spindle design created by Duo-Fast
Corporation.
"tool.dgn" Mechanical design example — 3D Model.

Mechanical drafting sample custom line styles
"gear.dgn"
Rendered
view of
"tool.dgn"
Mechanical drafting sample custom line styles

The "mechlsty.rsc" line style library has these line styles that
are useful for mechanical draft:

Mechanical drafting level structures
Line Style Name

Center Line
Parting Line
Mechanical drafting level structures

This level structure is defined in "countwt.lvl", which is used
with the sample design file "countwt.dgn":
Level Num- Description

Name ber
W501 1 Counter Weight Shaft Support
Weldment
W502 2 Counter Weight Shaft
W503 3 Counter Weight Mounting Plate
W504 4 Counter Weight
W302 7 adjacent part
This level structure is defined in "mechdet.lvl", which is
used with "mechdet.dgn":

Name ber
detail 1 detail object lines
center 2 centerlines
dimensions 3 dimensions and related text
notes 4 notes
border 5 border text
This level structure is defined in "mechlay.lvl", which is used
with the seed file "mechlay.dgn":

Mechanical drafting glossary file
Level Num-
Name ber
part1 1
part2 2
: :
part20 20
This level structure is defined in "spindle.lvl", which is
used with "spindle.dgn":

Name ber
W101 1 Lower Spindle Weldment
W102 2 Lower Spindle Housing
W103 3 Lower Pulley
W104 4 Upper Pulley
W105 5 Lower Spindle Cap
W107 7 Spool Locator
W108 8 Brake Plate
W109 10 adjacent part
Mechanical drafting glossary file

The glossary file "mechdrft.gls" has examples of commonly
used mechanical drafting terms and abbreviations. There
are too many entries to list here.
Visualization project
The Visualization project component includes sample design files.

Visualization sample design files
Visualization sample design files

These sample visualization design files are supplied, most of
which are used with the Tutorial Workbook:
"animsets.dgn" Flat-panel monitor.
"defpath.dgn" Illustration of camera path for

animation.
"desklite.dgn" Office interior.
"dotrace.dgn" Illustration of parametric motion

for animation.
"ergoman2.dgn" Model of human form useful for
understanding animation.
"gears.dgn" Gear assembly.
"hirise.dgn" High-rise building.
"key2.dgn" Model of a spring used for annotation

key framing.
"litex1.dgn" Illustration of light sources for
rendering.
"mattute1.dgn" Statue.
"office2.dgn" Office interior.
"plangear.dgn " Gear assembly.
"poolanim.dgn" Above-ground pool.
"racecar.dgn " Racing car on racetrack.
"radios1.dgn" Table with lamp.
"teapot.dgn " Teapot.
"ujoint.dgn" U-joint assembly.
"windmill.dgn" Windmill.

Workspace Configuration
This chapter covers configuration variables and the four
types of files that define workspaces:
• Basic concepts of configuration variables are covered in

Configuration Variables (see page 3-1) .
• The User Configuration File (see page 3-5) determines which

workspace (project, user interface, and user preference file)
is active; it can also contain a user’s overrides of settings
in the project configuration file. The user configuration file
consists of configuration variable definitions.
• The Project Configuration File (see page 3-5) contains configuration

variable settings for a particular project. The project configuration
file consists of configuration variable definitions.
• The User Interface Modification Files (see page 3-36) contain

modifications to MicroStation’s default user interface.
• The User Preference Files (see page 3-38) contain

user preference settings.
Before discussing how the user configuration file and project

configuration files are used, some background information
about configuration variables is required.
Configuration Variables
The User Configuration File (see page 3-5) and the Project
Configuration File (see page 3-5) use configuration variables to
select a workspace and to affect MicroStation’s behavior.
MicroStation’s configuration consists of:
• The directories in which it finds or stores various types of files.

How MicroStation processes configuration variables
• The names of special-purpose files.
• Certain default settings.
• Other information about the system on which it runs.
This information is stored in configuration variable definitions.
How MicroStation processes configuration variables
Start-up
When MicroStation is started, it processes a set of files that

contain configuration variables in this order:
1 . All “system-level” configuration variable files (in MicroStation’s

“config\system” directory).
2 . All “application-level” configuration variable files (in

MicroStation’s “config\appl” directory).
3 . All “site-level” configuration variable files (in Bentley’s

“Workspace\standards” directory).
4 . The “user-level” configuration variables (in Bentley’s

“Workspace\users” directory).
5 . The “project-level” configuration variables (in Bentley’s

“Workspace\projects” directory tree).
As each level is processed, its settings are stored in memory.

MicroStation keeps all settings, segregated by level, in memory.
Determining configuration variable settings

When MicroStation needs to determine (“resolve”) a
configuration variable setting, it looks for the setting in
the various levels in this order:

Levels of configuration variables
1 . The user level.
2 . The project level.
3 . The site level.
4 . The application level.
5 . The system level.
If the configuration variable is not set at any level, MicroStation

looks for an operating system environment variable of the same
name. MicroStation uses the value of the configuration variable at
the highest level it is set (the first place it finds it).
If you compare the order in which the files are processed to the
hierarchy of the level settings, you see that the later the level is
processed, the higher its priority, with one exception: In order of
priority, the “project-level” configuration variables are on a lower
level than the “user-level” configuration variables, but MicroStation
processes the user-level configuration variables first.
MicroStation processes the user-level configuration variables

first because the user configuration file determines which project
configuration file is to be processed. The user configuration file
specifies and reads (“includes”) the settings in the appropriate Project
Configuration File (see page 3-5) , which specifies configuration
variable settings for a project component of the workspace. Therefore,
although the project configuration file is the last in time to be
processed, the user configuration file has the last word.
In examples of configuration variable definitions in this chapter, unless

otherwise noted, the workspace user is assumed to be “examples”
— that is, the user configuration file is "examples.ucf".
Levels of configuration variables

There are five levels of configuration variables, all of which
MicroStation maintains in memory:
• System-level configuration variables are the first to be

processed by MicroStation when it is started. They are set

Types of configuration variables
by MicroStation itself. Settings made at this level can be

overridden by settings at any higher level.
• Application-level configuration variables are the second to be
processed by MicroStation when it is started. They are usually set
by MicroStation related application programs. Settings made at
this level can be overridden by settings at any higher level.
• Site-level configuration variables are the third to be processed
by MicroStation when it is started. They are usually set by
a system or site manager to facilitate using MicroStation in
workgroups. Settings made at this level can be overridden
by settings at any higher level.
• Project-level configuration variables are the fifth to be processed
(after user-level configuration variables) by MicroStation when it
is started. They are usually set by a site or project manager to
facilitate using MicroStation in workgroups. Settings made at this
level can be overridden by settings at the user level.
• User-level configuration variables are the fourth to be
processed by MicroStation when it is started. The user
configuration file determines which project configuration file
is processed. User-level configuration variable settings take
precedence over all other level settings.
The first four levels in this list are meant to be set by system, site and
project managers using a text editor (see Configuration Variable File
Syntax on page 3-40). The user-level configuration variables may
freely be changed by each user with the Configuration Variables dialog
box without fear of disturbing any other user’s configuration. Since the
user configuration variables are highest in precedence, there is no need
for a user to modify configuration variable definitions at any other level.
Types of configuration variables

The types of configuration variables are as follows:
• Path configuration variables tell MicroStation where (in

what directory) to find files.
For example, if you specify a design file to open when starting
MicroStation, it searches for the design file in the directory or
directories specified by the MS_DEF configuration variable. The
first time you choose Open from the File menu, the first directory
specified by MS_DEF displays in the Open Design File dialog box.

User Configuration File
• Directory configuration variables tell MicroStation where to save

files. For example, MS_PLTFILES tells MicroStation where
to save plotfiles. The first time you click the OK button in
the Plot dialog box, the directory specified by MS_PLTFILES
displays in the Save Plot As dialog box.
• Filename configuration variables specify a file to use for a
particular purpose. For example, MS_DESIGNSEED specifies
the seed file MicroStation copies to create a new design file
(if you do not select a different seed file).
• Keyword configuration variables specify certain default settings.
For example, MS_LINKTYPE specifies the user data linkage
types recognized by the database server. The possible values or
“keywords” are “XBASE,” “DMRS,” “IX,” “ORACLE,” and “RIS.”
For more information about configuration variables, see Working

With Configuration Variables on page 3-7.
User Configuration File

The user configuration file has two basic workspace functions.
First, it contains values for any configuration variables set by
you, the user, to control MicroStation’s behavior. Second, it
specifies the active workspace components. For example, the
MS_USERPREF configuration variable setting points to the user
preference resource file that defines the active user preferences
component. (The user configuration file is the file that opens when
you choose Configuration from the Workspace menu.)
User configuration files have the suffix “.ucf” and are stored
in Bentley’s “Workspace\users” directory.
Project Configuration File

A user working alone with MicroStation could conveniently set every
configuration variable at the user level. Project configuration files
exist in order to facilitate sharing of configurations among users
in a workgroup. The settings in each user’s user configuration
file allow each user in a workgroup to customize MicroStation,
while the shared settings of the project configuration file provide
uniformity within the workgroup. The project configuration file is

Modules
the file that is selected when you select the project component of
a workspace in the MicroStation Manager dialog box.
The role of the project configuration file in a workspace is to specify the
data files in a particular module that are used in the workspace.
Modules
The module data for the sample workspace project components
provided with MicroStation are stored in subdirectories of Bentley’s
“Workspace\projects\examples” directory.
For example, the architectural module comprises:
• Sample architectural design files in Bentley’s

“Workspace\projects\examples\arch\dgn” directory.
• Sample architectural seed files in Bentley’s
“Workspace\projects\examples\arch\seed” directory.
• Sample architectural cell libraries in Bentley’s
“Workspace\projects\examples\arch\cell” directory.
• Sample architectural level structure files in Bentley’s
“Workspace\projects\examples\arch\data” directory.
• A sample architectural glossary file in Bentley’s
“Workspace\projects\examples\arch\data” directory.
• Sample line style libraries in Bentley’s
“Workspace\projects\examples\arch\symb” directory.
These modules are just examples, and you can use configuration
variables to point to various files throughout the modules. The
advantage of creating modules this way is that you can place
the “Workspace\projects” directory and subdirectories on a
network and make them read-only with the exception of the
“dgn” subdirectories. Everyone in a workgroup can use the
data, but the data’s integrity is assured.

Working With Configuration Variables

User-level configuration variables can be set in dialog boxes,
as described in this section.
System-, application-, site-, and project-level configuration variables

must be edited with a text editor using the syntax explained in
Configuration Variable File Syntax (see page 3-40) .
General Procedure — To Modify User-level

Configuration Variables
1. From the Workspace menu, choose Configuration.
The Configuration Variables dialog box opens.
Configuration
Variables
dialog box
2. In the Category list box, select the category that contains

the configuration variable you wish to modify. For a
list of all configuration variables by category, see User
configuration variables on page 3-12.
or
In the Category list box, select All (Alphabetical) or All (By
Level), scroll through the configuration variables in the list
box to the right, and select the desired variable.
The controls for setting the definitions of that category of
configuration variables are displayed. In the Expansion field, the

expansion of the variable is shown. In the Description field, a

description of the variable and its name are shown.
3. Use the controls to modify the definition. The procedure
varies for the different Types of configuration variables (see
page 3-4) . See one of the following:
To set a path configuration variable (see page 3-8) .
To set a directory configuration variable (see page 3-9) .
To set a filename configuration variable (see page 3-10) .
To set a keyword configuration variable (see page 3-11) .
(Experienced users familiar with configuration variable syntax:
See also To edit a configuration variable on page 3-11.)
4. Click OK.
If you modified any configuration variable definitions, an alert
box opens, asking whether you want to save the changes in
the user configuration file, save the changes only in memory
for the current session, or cancel the changes.
5. In the alert box, click Yes to save the changes to the user
configuration file, click No to save the changes only in memory for
the current session, or click Cancel to cancel the changes.
If you use a text editor to look at the definition of a configuration

variable in a configuration file, you may find that the definition
contains other configuration variables and conditional syntax.
The definition is often text that must be expanded into the actual
names of directories, paths, files, and so on. When you select a
configuration variable in the Configuration Variables dialog box, the
Expansion field shows the expansion of the variable.
To set a path configuration variable

1. With the path configuration variable selected in the Configuration
Variables dialog box, click the Select button.
The Select Path dialog box opens. In the Directory List,
directories, if any, already included in the configuration
variable’s expansion are shown.

Select Path
dialog box
2. To add a directory to the configuration variable’s definition, select

the directory from the Directories list box (or key in the directory
specification in the Directory field), then click the Add button.
3. To remove a directory from the configuration variable’s definition,
select it in the Directory List and click the Remove button.
4. Click the Done button.
To set a directory configuration variable

1. With the directory configuration variable selected in the
Configuration Variables dialog box, click the Select button.
The Select Directory dialog box opens. In the field above the
Directories list box, the directory (if any) already included in
the configuration variable’s expansion is shown.

Select
Directory
dialog box
2. To change the directory in the configuration variable’s definition,

select the desired directory in the Directories list box (or key
in the directory specification in the Directory field).
3. Click OK.
To set a filename configuration variable

1. With the filename configuration variable selected in the
Configuration Variables dialog box, click the Select button.
The Select File dialog box opens. In the Files list box,
the file (if any) already included in the configuration
variable’s expansion is shown.
Select File
dialog box

2. To change the file in the configuration variable’s definition,

select the desired file in the Files list box or key in the
filename in the Files field. (If necessary, use the Directories
list box to select the proper directory.)
3. Click OK.
To set a keyword configuration variable

1. With the configuration variable selected in the Configuration
Variables dialog box, click the Edit button.
(The Select button is dimmed because keywords cannot be selected.)
The Edit Configuration Variable dialog box opens.
Edit
Configuration
Variable
dialog box
2. In the Edit Configuration Variable dialog box’s New Value field,

enter the desired keyword. (Although keywords are not case
sensitive, uppercase letters are used by convention.)
The keyword is also shown in the Expansion field.
3. Click OK.
To edit a configuration variable

1. With the configuration variable selected in the Configuration
Variables dialog box, click the Edit button.
The Edit Configuration Variable dialog box opens.

User configuration variables
2. In the Edit Configuration Variable dialog box’s New Value field,

edit the configuration variable definition. (Although keywords are
not case sensitive, uppercase letters are used by convention.)
The Expansion field shows the expansion of the definition
in the New Value field.
3. Click OK.

This table lists user configuration variables by category.
Cate- Variable Short name Description

gory
Archive MS_ARCHIVE "Archive Search Search path for
Path" archive files.
MS_ARCHIVE- "Archive Class Search path for

CLASS Search Path" archive class
files.
MS_KEY- "KeyPair File List" Digital
PAIRLIST signature
KeyPair file
list.


gory
Cells MS_CELL "Cell Library Search path(s)
Directories" for cell
libraries.
MS_CELLLIST "Cell Library List" List of cell
libraries to be
searched for
cells not found
in the current
library.
MS_CELLSE- "Cell Selector Directory
LECTORDIR Directory" for Cell
Selector button
configuration
(.csf) files.
MS_CELLSE- "Cell Selector File" List of cell
LECTOR libraries to be
searched for
cells not found
in the current
library.
MS_CELLOUT "Output Cell Default
Libraries" directory for
newly created
cell libraries.
MS_MENU "Menu Cells" Cell library
file containing
menu cells.
MS_TUTLIB "Tutorial Cell Cell library
Library" containing
tutorial cells.


gory
Colors MS_DEFCTBL "Default Color Default color
Table" table if design
file has none.
MS_RMENC "Right Menu Color Default menu
TBL Table" colors (dialog
boxes, borders,
etc.) for right
screen —
specifies a color
table (.tbl) file.
MS_LMENC "Left Menu Color Default menu
TBL Table" colors (dialog
boxes, borders,
etc.) for left
screen —
specifies a color
table (.tbl) file.


gory
Database MS_DBASE "Database Files" Search path(s)
for database
files.
MS_SERVER "Server Loader" MDL
application
to load the
database
interface
software.
MS_DBEXT "Database Server" The database
interface
“server”
application.
MS_LINKTYPE "Database User data link-
Linkages" age types rec-
ognized by the
database inter-
face software.
See MS_LINK-
TYPE.
MS_DBMODE "Xbase File File sharing
Sharing" flag for Xbase
— “shared” or
“nonshared.”


gory
Data MS_HTML "HTML Template Directory
Files DGNDIR Directory" containing
template
design files
used to
generate
cell images
for HTML
documents.
MS_SETTINGS "Settings Resource" Open settings
file.
MS_SETTING- "Settings Output Directory for
SOUTDIR Directory" newly created
settings files.
MS_SETTINGS- "Settings Directory" Directory
DIR containing
settings files.
MS_LEVEL- "Level Names" Directory
NAMES containing
level structure
files.
MS_GLOSSARY "Glossary Terms" List of files for
use with the
Glossary dialog
box (Utilities
menu > Text
Glossary).
Design MS_DGNAPPS N/A List of MDL
Applica- applications
tions to load
automatically
when a design
file is opened.


gory
Engi- MS_WE- "Weblib history" History file
neering BLIB_HISTORY for the Weblib
Links shared library.
MS_BOOK- "Image bookmarks" Bookmark file
MARKS_IMAGE for remote
images.
MS_BOOK- "Resource Bookmark file
MARKS_RSC bookmarks" for remote
resource files.
MS_BOOK- "Archive Bookmark file
MARKS_ARC bookmarks" for remote
HIVE archives.
MS_BOOK- "Cell library Bookmark file

MARKS_CELL bookmarks" for remote cell
libraries.
MS_BOOK- "DGN bookmarks" Bookmark file
MARKS_DGN for remote
design files.
MS_REFA- "RefAgent data file" File containing
GENTDATA URL
information for
the Reference
File Agent.
MS_WEB "Kiosk mode" Set to 1 to turn
KIOSKMODE on kiosk mode.
MS_WEB- "Special filetype Specifies a file

TYPESFILE handling" that contains
special
handling
instructions
for various file
types.


gory
Engi- MS_WEB- "Weblib local Directory in
neering FILES_DIR storage" which copies
Links of remote files
are stored.
MS_WEB- "Download Sets the
DOWNLOAD- directory" directory in
DIR which WWW
downloads are
stored.
MS_BROWSER- "Reparent browser" When set to
MAKECHILD- 1, the current
WINDOW browser is
reparented
inside of the
MicroStation
main window,
allowing the
viewer to
always be seen.
MS_USEEX- "External browser Sets an
TERNAL- name" external
BROWSER browser.


gory
MDL De- MS_RDESYS- "Runtime resource Text to be
velop- INC compiler" inserted at the
ment beginning of
the command
line by the
resource
compiler DLM.
Generally used
to specify the
location of
include files.
MS_DBG- "MDL Source" Location of
SOURCE source code
for MDL
applications
(used by MDL
debugger).
MS_MDLTRACE "MDL Trace" If set,
additional
debugging
print
statements are
provided when
debugging
MDL
applications.
MS_AS- "Assertion Failure Format of
SERT_MES- Message" assertion
SAGE messages.
The default
is Assertion
Failure %s
%s(%d).


gory
MDL De- MS_AS- "Assertion Failure Specifies
velop- SERT_HAN- Handling" handling of
ment DLING assertion
failure:
• 0 (default)
— display
error
message
• 1 — log
error
message
• 2 —
stop in
debugger
MS_DEBUG- "Debug Fault" If set,
FAULT automatically
invoke the
debugger
when a fault
is detected
while an MDL
application is
active.
MS_DEBUG "Time Out" If set to an
integer with
bit 1 on, do not
time out.
MS_TRAP "Exception Exception
Handling" handling flag
— “ALL”
(default),
“MDL,” or
“NONE.”


gory
OLE MS_OLE- "Embed Reference If set, reference
SERVE_EM- Files" files are
BED_REFFILES embedded
along with the
master design
file.


gory
Opera- MS_AUTORE- "Auto-restore If set to 1, the
tion STORESTA- Status Bar" status bar is
TUSBAR restored to
its default
appearance
whenever the
pointer is
moved within.
MS_EN- "Enhanced If set to 1,
HANCEDPRE- Precision" enhanced
CISION precision
enabled. If
set to 0, is
disabled. A
change in this
setting takes
effect after the
design file is
reopened.
MS_FKEYMNU "Function Key Open function
Menu" key menu file.
MS_ACCUD- "AccuDraw Text file listing

RAWKEYS Shortcuts" AccuDraw
shortcut keys.
MS_GRAPHIC- "Graphics Sets the name
SACCELERA- Accelerator" of the graphics
TOR accelerator
application.
MS_BACKUP- "Back Up Before If set, the
BEFORECOM- Compress" active design
PRESS file or attached
cell library is
backed up to
the MS_TMP
directory
before a
Compress
request is
executed.


gory
Opera- MS_RASTER- "Raster Scan" If set to
tion SCAN 1, raster
reference
scanning
enabled. If
set to zero,
disable scan.
MS_SAVEMENU "Attached Menus" File containing
information
about attached
menus.
MS_APPMEN "Application Location of
Menus" application and
sidebar menus.
MS_WORK "Workspace Sets how
SPACEOPTS Options" MicroStation
Manager
displays
workspace
options: 0
or not set
(default) =
workspace
remains same;
1 = workspace
options visible
but disabled;
2 = workspace
options hidden,
MM resized.


gory
Opera- MS_USECOM- "Use Command If set, 0 sets
tion MANDWINDOW Window" the status
bar interface,
and 1 sets
the Command
Window
interface. If
not set, the
Style setting in
MicroStation
Manager
determines the
interface style.
MS_FILEHIS- "File History" If set,
TORY MicroStation
saves the last
four files and
directories for
each file type.
MS_SYSTEM "Escape to O.S." If set,
MicroStation
allows the user
to escape to
the operating
system.


gory
Opera- MS_READONLY "Read Only" If set, the
tion active design
file is read-only.
MS_NOEOF_MS- "No EOF Message" If set
GFILE (manually),
displays the
contents of this
file when a “no
end-of-file”
error is
encountered.
Setting this
variable also
prevents the
file from being
opened.
MS_DISALLOW- "Disallow Full If set, you
FULLREFPATH Ref Path" cannot save
a reference
file attachment
with a full path
specification.
Plotting MS_BATCH- "Batch Plot Name of
PLT_SPECS Specifications" the file that
contains the
batch plotting
specifications.
MS_PLTFILES "Output Directory" Directory for
plotting output
files (plotfiles).
MS_PLOTINI "Plot Configuration Directory
Files" for plot
configuration
files.
MS_PLTR "Plotter Driver File" Name of plotter
driver file.
MS_PENTABLE "Pen Tables" Search path for
pen table files.


gory
Primary MS_DEF "Design Files" Search path(s)
Search for design files.
Paths
MS_RFDIR "Reference Files" Search path(s)
for reference
files.
MS_MDLAPPS "Visible MDL Search path(s)
Applications" for MDL
applications
displayed in
the MDL dialog
box.
MS_MDL "MDL Applications" Search path(s)
for MDL
applications
or external
programs
loaded by MDL
applications.
MS_MACRO "Macros" Search path for
macros.
MS_RSRCPATH "Resource Files" Search path(s)
for resource
files loaded
by MDL
applications.
MS_LI- "Library Path" Search path for
BRARY_PATH dynamic link
libraries.


gory
Render- MS_MTBL "Material Tables" Search path(s)
ing/Im- for material
ages tables.
MS_MATERIAL "Material Palettes" Search path(s)
for material
palettes.
MS_PATTERN "Pattern Maps" Search path(s)
for pattern
maps.
MS_BUMP "Bump Maps" Search path(s)
for bump maps.
MS_IMAGE "Images" Search path(s)
for images.
MS_IMAGEOUT "Image Output" Directory in
which created
image files are
stored.
MS_SHAD- "Shadow Maps" Directory
OWMAP where shadow
maps will be
read from and
written to.
MS_LIGHTING "Lighting Files" Directory
where IES
lighting data
will be stored.
MS_RENDER- "Rendering File in which
LOG statistics log" rendering
statistics are
logged.


gory
Seed MS_SEEDFILES "Seed File Location" Search path(s)
Files for all seed
files.
MS_DE- "Default Design Default seed
SIGNSEED File Seed" file.
MS_CELLSEED "Default Cell Default seed

Library Seed" cell library.
MS_TRANSEED "Default Default

Translation Seed" seed file for
DWG, CGM,
and IGES
translations.
MS_SHEET- "Drawing Sheet Seed sheet
SEED Seed File" file drawing
composition,
DWG import,
and IGES
import.
MS_USERPREF- "User Preference Name of seed
SEED Seed" file used to
create user
preference
resource file.
Symbol- MS_SYMBRSRC "Symbology List of
ogy Resources" symbology
resource files
— last one in
list has highest
priority.


gory
System MS MicroStation Base The
Env(iron- Dir MicroStation
ment) root
installation
directory used
by MDL sample
“make” files.
MS_CONFIG "Main Configura- Main
tion File" MicroStation
configuration
file —
sets up all
configuration
variables.
MS_EDG "EDG Directories" Directories
used by
EDG (not
MicroStation).
RSC_COMP "Resource Compiler Text string to
Command" be inserted at
the beginning
of the
command line
by the resource
compiler (used
to specify
where to search
for include
files).


gory
System MDL_COMP "MDL Compiler Text string to
Env(iron- Command Line" be inserted
ment) at the
beginning of
the command
line by the
MDL compiler
(used to specify
where to search
for include
files).
BMAKE_OPT "BMAKE Options" Command line
options for
BMAKE. Used
to search for
bmake include
(.mki) files.
MS_DEBUG- "Extended Malloc" If set (to the
MDLHEAP base name
of an MDL
application
or “ALL),
use extended
malloc for
debugging.
Tags MS_TAGOUT- "Tag Output" Output
PUT directory
for tag set
libraries.
MS_TAGRE- "Tag Reports" Output
PORTS directory for
tag reports.
MS_TAGTEM- "Tag Templates" Directory
PLATES containing
tag report
templates.


gory
Temp MS_BACKUP "Backup Files" Default
and directory for
Backup backup files.
Files
MS_TMP "Temporary Files" Directory for
temporary
files created
and deleted by
MicroStation.
MS_SCR "Scratch Files" Directory for
scratch files
created by
MicroStation.
Transla- MS_CGMIN "CGM Input Input directory
tion — Directory" for CGM
CGM translations.
MS_CGMOUT "CGM Output Output
Directory" directory
for CGM
translations.
MS_CGMLOG "CGM Log Files" Output
directory for
CGM log files.
MS_CGMTA- "CGM Configura- Directory
BLES tion Tables" containing
the CGM
translation
tables.
MS_CGMINSET "CGMIN Settings Settings file
File" for the CGMIN
application.
MS_CGMOUT- "CGMOUT Settings Settings file for
SET File" the CGMOUT
application.


gory
Transla- MS_DWG- "DWG Wizard" Configuration
tion — WIZRD variable to
DWG enhance the
DWG Wizard.
MS_DWGIN "DWG Input Input directory
Directory" for DWG
translations.
MS_DWGOUT "DWG Output Output
for DWG
translations.
MS_DWGLOG "DWG Log Files" Output
directory for
DWG log files.
MS_DWGTA- "DWG Configura- Directory
BLES tion Tables" containing
the DWG
translation
tables.
MS_DWGINSET "DWGIN Settings Settings file
File" for the DWGIN
application.
MS_DWGOUT- "DWGOUT Settings Settings file for
SET File" the DWGOUT
application.
MS_DWGCODE- "DWG Code Page" Code page to
PAGE be set in the
DWG/DXF file
(export only).


gory
Transla- MS_GRDIN "GRD Input Input directory
tion — Directory" for GRD
GRD translations.
MS_GRDOUT "GRD Output Output
for GRD
translations.
MS_GRDLOG "GRD Log Files" Output
directory for
GRD log files.
MS_GRDINSET "GRDIN Settings Settings file for

File" GRD import.
MS_GRDOUT- "GRDOUT Settings Settings file for

SET File" GRD export.
Transla- MS_IGESIN "IGES Input Input directory
tion — Directory" for IGES
IGES translations.
MS_IGESOUT "IGES Output Output
for IGES
translations.
MS_IGESLOG "IGES Log Files" Output
directory for
IGES log files.
MS_IGESINSET "IGESIN Settings Settings file for
File" IGES import.
MS_IGESOUT- "IGESOUT Settings Settings file for

SET File" IGES export.


gory
User MS_UCM "User Commands" Search path(s)
Com- for user
mands commands.
MS_INIT "Startup User Name of user
Command" command to
be executed at
start-up.
MS_EXITUC "Exit User Name of user
Command" command to
be executed
at exit.
MS_NEWFILE "New File User Name of user
Command" command to be
executed when
a new file is
opened.
MS_APP "Apps from “TSK” Search path(s)
statements" of applications
started
from “TSK”
statements
in user
commands.
This table lists uncategorized configuration variables:
Variable Description
CLASSPATH Path to Java/JMDL classes.
HISTORY_MAX_MI- The number of minor versions

NOR_VERSION for the Limit History command
to preserve in the history file.
MSDIR Product root installation
directory.
MSLOCAL Specifies the base directory
path for where the required
directory portions (that is, local
for a network installation) of
MicroStation are installed.

MS_BASICEXT_LOAD List of MDL applications
that implement extensions
to the BASIC language
(MS_BASIC_LOAD).
MS_CACH Optional cache ID string
for MicroCSL.
MS_CMDTABLE_LOAD List of MDL applications
that will have their key-in
tables auto-loaded.
MS_CMDWINDRSC Command Window resource file.
Default is used if undefined.
MS_CODESET MDL application for handling
multi-byte character sets.
MS_DATA Directory for data files created
or used by MicroStation.
MS_DEFCHARTRAN Default character translation
table.
MS_DGNOUT Directory containing design
files created as a result of
“on the fly” translation from
other file formats.
MS_DY- Server to which on-line help
NAWEB_HELPSERVER requests are directed.
MS_EXE Directory containing the

MicroStation executable
program.
MS_GALLERYCELL Default gallery cell to which
to connect.
MS_GALLERYLIB Cell library used by the chart
application.
MS_GUIHAND Identifies auxiliary handlers.
MS_HELPPATH Path to help files.
MS_INITAPPS List of initial start-up MDL

applications.

User Interface Modification Files
MS_OLDUSERLICENSE File that contains old user license
information. Required for when
installing a product upgrade.
MS_OPENDESIGNFILE- Initial file filter for the
FILTER MicroStation Manager and
Open Design File dialog boxes.
MS_RIGHTLOGICKB If set to 1, keyboard input
is right to left.
MS_RSRC Main MicroStation resource file.
Typically set to “ustation.rsc.”
MS_TUT_UCMS Directory containing user
commands that drive tutorials.
MS_UNDO If set, specifies the amount of
memory, in bytes, allocated to the
undo buffer, thereby overriding
the Undo Buffer (KB) preference.
MS_USERLICENSE File containing MicroStation
license information.
MS_USERPREF User preference resource file.
NODE If manually set to on the node

name is stored in the file
locking semaphore file. Only
used when semaphore file
locking is turned on.
USER If manually set to on the user
name is stored in the semaphore
file. Only used when semaphore
file locking is turned on.
WRK_DD_IGDS Directory containing IGDS
UCMs.

Customizations of MicroStation’s user interface are stored in
user interface modification files. In the sample workspaces

provided with MicroStation, the user interface modification

files are grouped in the various subdirectories under Bentley’s
“Workspace\interfaces\MicroStation” directory. When you
choose a user interface in the MicroStation Manager dialog
box, you are specifying a directory from which all user
interface modification files are read.
Each time you modify the user interface, a user interface
modification file is created.
If the part of the interface modified is part of MicroStation’s “core,” then

the filename of the user interface modification file created is “ustn.” If
the tool box or dialog box modified is provided by an MDL application,
the filename of the user interface modification file is the filename of
the MDL application. Examples of filenames of MDL applications that
provide parts of the user interface are “igen” and “userpref.”
The suffix of each user modification resource filename is an “m”

followed by a number from “01” to “99.” Each time an interface
modification file is saved with the same filename, the number in
its suffix is incremented. Therefore, the files might be named
“ustn.m01,” “ustn.m02,” “ustn.m03,” “igen.m01,” and so on.
There are three other levels of modification resource files in addition

to user level: project, site, and system. Like user configuration
files, each category of modification resource file has an associated
priority and a unique filename suffix. The table below shows each
category, its file suffix, and the associated priority.
Level Filename suffix Priority

User .m01-.m99 1 (highest)
Project .p01-.p99 2
Site .s01-.s99 3
System .r01-.r99 4 (lowest)
When you create an interface workspace component, all the
modifications you have made to the default user interface
are “inherited” by the new interface. That is because
MicroStation first processes any user, project, site, and system
interface modification files specific to the new interface before
processing any user interface modification files in Bentley’s
“Workspace\interfaces\MicroStation\default” directory. Where

User Preference Files
the “default” modification files are different, the files in the active
user interface’s subdirectory override them.
For information about modifying MicroStation’s user interface

(and creating user interface modification files), see Customizing
the User Interface on page 4-1.
User Preference Files

When you choose Preferences from the Workspace menu, the settings
in the active user preference file are displayed in the Preferences dialog
box. Generally, user preferences reflect what they are named for, the
personal preferences of a user in operating MicroStation, rather than
settings that are important to maintain across a workgroup.
For information about using the Preferences dialog box, see

Setting User Preferences in the User Preferences chapter
of the on-line User’s Guide.
Configuration Variable Files

MicroStation uses configuration variable files to get values for
settings that vary from system to system and from user to user.
From a development standpoint, MicroStation configuration
variables are simply a mechanism for “expanding” (translating)
one text string into another.
For example, MicroStation needs to find its main resource file. Rather
than always looking for a file named "ustation.rsc" "msdraft.rsc" in
a specific directory, it expands the configuration variable MS_RSRC
(defined in the configuration variable file) to get a file name and
location. That way (assuming the configuration variable file is correct)
MicroStation finds the file regardless of its name and location.
Each configuration variable has two parts — its name and its
definition. Variable definitions can be literal strings or combinations
of strings and references to other variables.
When MicroStation needs the value of a variable, it looks in the

variables table (kept in memory) to find the definition. If the
variable is found, it then expands any nested variable references

The Main Configuration Variable File
in the definition. If the variable cannot be found, it then attempts

to find a system-level environment variable of the same name. If
a system-level environment variable is defined, MicroStation uses
that value as if it were defined in the variables table.
In the Windows operating system, the system-level environment

variables are defined using the “System” utility in the Control
Panel or the SET command.
The Main Configuration Variable File

The system-level environment variable MS_CONFIG should point
to "mslocal.cfg", which sets installation specific values and then
includes (processes) the main configuration variable file:
Level Defined By
System MicroStation
Application Third-party applications
Site System manager
Project Project manager
User Users
It begins by assigning these configuration variables, which define
directories in which additional configuration variables files may
be located: _USTN_SYSTEM, _USTN_APPL, _USTN_SITE,
_USTN_PROJECT, and _USTN_USER.
By default, these _USTN_xxx configuration variables point

to subdirectories of Bentley’s “MicroStation\config” directory.
However, they can be overridden with operating system
environment variables with the same names.
The "msconfig.cfg" file includes (processes) all of the configuration

variable files in each of the system, application, and site directories (in
that order). Within each directory, it includes all of the configuration
variable files (*.cfg) in alphabetical order. Because the variable files
are included in this order, application level configuration variables
can override system-level ones, site level configuration variables
can override application level ones, and so on.

Configuration Variable File Syntax
After processing all of those files, the "msconfig.cfg" file includes a

single user configuration variable file. You can designate the name of
your user configuration variable file with the _USTN_USERNAME
system-level environment variable. The project configuration variable
file is typically included by reference in the user configuration
variable file as a means of implementing workspaces.
For more detailed information, see the comments in "msconfig.cfg",

which is installed in Bentley’s “MicroStation\config” directory.

Configuration variable files are text files that consist of a series
of lines. Each line contains a configuration variable name
and definition in the following syntax:
<VARIABLENAME> <operator> <new_value> # comment
or a preprocessor directive in this syntax:
%<preprocessor directive>
VARIABLENAME is the name of the configuration variable defined.

Nearly all variable names used by MicroStation begin with “MS_” or
“_USTN_.” Variables whose names begin with an underbar ( _ ) are
not displayed in the Configuration Variables dialog box.
Variable names can contain only alphanumeric characters (A-Z, 0-9)

and must be at least two characters long. Although variable names are
not case sensitive, uppercase letters are used by convention. There is
no limit on the length of a variable name, but as a practical matter
it should be kept under 32 characters. White space (space or tab
characters) before and after the variable name is ignored.
Available values for operator are as follows:
Operator Meaning
= Assign new_value to VARIABLENAME.
: Assign new_value to VARIABLENAME only
if that variable does not already exist.

Operator Meaning
+ Append new_value to current value of
VARIABLENAME. Uses a space as a separator.1
>2 Append directory or file lists defined by
new_value to a variable definition that defines a
path. If no current value for VARIABLENAME
exists, this is equivalent to the = operator.
Otherwise, it appends a path separator character,
a semicolon (;), and then new_value.
<3 “Prepend” directory or file lists defined by
new_value (to the beginning of) a variable
definition that defines a path. If no current
value for VARIABLENAME exists, this is
equivalent to the = operator. Otherwise,
it prepends new_value followed by a path
separator character, a semicolon (;).
1 This operator could be useful for building a string, but it should not
be used for directory or file lists.
2 This character points towards the end of the existing directory of file
lists, where the new value is added.
3 This character points to the beginning of the existing directory of file

lists, where the new value is added.
Anything after a # on a line is treated as a comment and is ignored.
File path names should be entered using the forward slash (/). Windows
converts all forward slashes (/) in new_value to backslashes (\). Also,
all directory definitions should end with a trailing forward slash.
This is an example of a valid directory definition:
MS_DEF = /network/dgn/
These definitions are not valid:
MS_DEF = /network/dgn #no trailing slash

MS_DEF = \network\dgn\ #backslashes

Variable definition references
Variable definition references

A variable definition can contain references to other variables.
References to other variables are made with the following syntax:
Reference Meaning
$(VARIABLEREF) Expand VARIABLEREF when this

variable is used.
${VARIABLEREF} Expand to current value of

VARIABLEREF.
MicroStation recognizes the following kinds of variable
definition references:
Reference Returns
dev() device
dir() directory
devdir() device and directory
parentdir() parent directory
parentdevdir() device and parent directory
basename() filename without extension
filename() filename with extension
ext() file extension
noext() Complete file specification

without extension
first() first path from a list of paths
concat() concatenated string
build() constructs a definition from

pieces of variables
For example, consider configuration variable MS_EXAMPLE_FILE
with the definition "D:\Bentley\Workspace\MyProject\3dcells.cel".
• $(dev (MS_EXAMPLE_FILE)) expands to "d: ".

• $(parentdir (MS_EXAMPLE_FILE)) expands to
“\Bentley\Workspace”.
• $(filename (MS_EXAMPLE_FILE)) expands to "3dcells.cel".

MicroStation-defined variables
Now consider configuration variable MS_EXAMPLE_PATH with

the definition "d:\cell\mycells\;c:\cell\;g:\mycells\".
• $(first (MS_EXAMPLE_PATH)) expands to "d:\cell\mycells\".

• $(build (“c:”,first (MS_EXAMPLE_PATH),”patterns”, ext (
(MS_EXAMPLE_FILE)) expands to "d:\cell\mycells\patterns.cel".
MicroStation-defined variables
MicroStation defines one of the following configuration variables
to indicate which software is running:
Variable name Defined when

_MICROSTATION MicroStation is
running.
_MSDRAFT MicroStation
PowerDraft is running.
_MSPOWERSCOPE MicroStation
PowerScope is running.
_PRJREVIEW Project Review is
running.
Preprocessor directives
Preprocessor directives control the way that MicroStation processes
configuration variable files. Preprocessor directives always begin
with %. The following preprocessor directives are available:

Preprocessor directives
Directive Meaning
%include<filename> Include (process) another configuration
variable file. filename can contain
variable references. In addition, it can
contain the wildcard character (*), in
which case all files that satisfy the
wildcard specification are included.
%if <expression> Execute the following lines if expression
is true. Expressions can be composed
of Boolean combinations of:
• defined () - true if variable
is defined.
• exists () - true if file exists.
• || - logical OR.
• && - logical AND.
• ! - negate.
• ( ) - grouping.
%else Execute the following lines if the
last %if was false.
%elif <expression> Execute the following lines if the last %if
was false and expression is true.
%endif End of conditional block.
%error <string> Print string and exit MicroStation.

%undef <varName> Undefines and deletes the configuration
variable varName. (To keep the variable
defined with a translation of NULL,
use varName = <space>).
%lock <varName> Locks the configuration variable to
its current value.
For example, assume the following system-level environment
variables are defined before MicroStation starts:

Debugging Variable Definition Files
Variable Current value

name
MS_DEF "c:\dgn\"
PROJDIR "\project33\"
When started, MicroStation processes this configuration variable file:
# make sure the project directory is set up

PROJDIR:/noproj/ # if no project is active
# define my design file directories
MS_OLDDEF = ${MS_DEF}
%if defined (TRAINING)
MS_DEF = c:/ustation/dgn/
%endif
MS_DEF < f:/usr2/dgn/ # a network drive
PROJDGN : $(PROJDIR)dgn/ # set up accounting information
ACCNTFILE = $(PROJDIR)accnt.dat
The variables table (stored in memory by MicroStation) contains

the information in the first two columns of the following chart.
When MicroStation expands a variable definition, it will have the
value of the corresponding item in the third column:
Variable name Definition Expands to

MS_DEF "c:/ustation/dgn/;f:/usr2/dgn/
"c:\ustation\dgn\;f:\usr2\dgn\
" "
PROJDIR “/project33/” “\project33\”
MS_OLDDEF "c:/dgn/"
PROJDGN “$(PROJDIR)dgn/” “\project33\dgn\”
ACCNTFILE "$(PROJDIR) "\project33\accnt.dat"

accnt.dat"

To determine whether your configuration variable files
are being processed properly, start MicroStation with the
-debug=n command line switch.
• At a command prompt, enter: ustation -debug=n

or append -debug=n to the Target field in the MicroStation

program item’s properties dialog box (Shortcut tab).
where n is a value from 1 to 5.
MicroStation displays the names of all of the configuration

variable files it processes and the names and values for all
variable definitions. Then MicroStation exits.
Use one of the following values for n:
Value of n Type of report

1 Brief report that shows the current
string value of each configuration
variable as it is processed.
2 In addition, shows the current
translation of each configuration
variable as it is processed.
3 In addition, shows conditional break
information by displaying the line
number when each if preprocessor
directive is processed.
4 In addition, prints final translations
of all configuration variables at
the end of the report. This is
the default setting.
5 In addition, shows final values
of all configuration variables at
each level (system, application,
site, project, user).
For most purposes, the value 4 (the default setting) gives the
most meaningful report: It shows the values of the configuration
variables as they exist while MicroStation is running.
The information in the report is saved as ASCII text in the

file “msdebug.txt” in the current directory.

Customizing the User
Interface
Perhaps the most noticeable way of customizing a workspace is
to modify its user interface component. You can customize any or
all of the parts of the active workspace user interface:
1 . Tool Boxes (see page 4-1)
2 . Pull-Down Menus (see page 4-15)
3 . View Control Bars (see page 4-22)
The Workspace Components dialog box is used to select and activate

user interfaces and other types of workspace components. For the
procedure, see Workspace Components on page 1-1.
The following aspects of the MicroStation user interface are not parts
of the workspace user interface, but you can also customize them:
• AccuDraw Keyboard Shortcuts (see page 4-26)
• Function Key Menus (see page 4-27)
• Digitizing Tablet Menus (see page 4-29)
• Tutorials (see page 4-41)
Tool Boxes
The Customize dialog box (Workspace > Customize) is used to
customize tool boxes — both “parent” tool boxes (referred to as
tool “frames” in the software) like the Main tool frame, and other,
“normal” tool boxes. It is also used to customize menu bars, view
borders and interface settings, and to convert palettes.

Customizing the User Interface
Tool Boxes
General Procedure — To customize

“parent” tool frames
1. From the Workspace menu, choose Customize.
The Customize dialog box opens. The following tabs are on
the dialog box: Tool Boxes, Tool Frames, Menu Bar, View
Border, Interface Settings, Convert Palettes.
2. From the tab menu, choose Tool Frames.
3. From the Edit Tool Frame combo box, select Main.
or
Once the combo box is selected, type the name of
the tool frame, Main.
The destination list box lists the child tool boxes in the Main tool
frame (and any tools added during previous customizations).
Customize
dialog box
with the Tool
Frames tab
displayed
4. If you are not customizing the Main tool frame, create a

“parent” frame box. See To create and open a tool box
or tool frame on page 4-5.
5. Make the desired modifications to the tool box:
Modification type
Rearranging child tool boxes
(see page 4-8)
Inserting child tool boxes
(see page 4-8)

Tool Boxes
Modification type
Rearranging tools (see page 4-9)
Inserting tools (see page 4-10)
Modifying tools (see page 4-13)
Most modification procedures are simple “drag-and-drop”
operations. As you drag the entry for a tool or tool box, a square
outline pointer indicates the tentative position of the entry.
6. Click the Save button.
The tool frame (if not already open, opens) blinks to indicate
the effect of the modification.
7. Repeat steps 4–6 for each additional “parent” tool frame
you want to create or modify.
If you created any tool frames, they are listed in the Tool Boxes
dialog box (Tools > Tool Boxes…). You can open them using that
dialog box. Also you can identify user-created tool frames by
a bolder font than appears in the regular tool boxes.
To customize normal tool boxes

The Customize dialog box opens.
2. From the tab menu, choose Tool Boxes (if not already chosen).
Customize dialog
box with the
Tool Boxes tab
displayed

Tool Boxes
3. From the Edit Tool Box combo box, select an existing

tool box. See To select and open an existing tool box
for customization on page 4-5.
or
Once the combo box is selected, type the name of the tool box.
or
Create a tool box. See To create and open a tool box
or tool frame on page 4-5.
4. Make the desired modifications to the tool box.
Modification type
Rearranging tools (see page 4-9)
Inserting tools (see page 4-10)
Modifying tools (see page 4-13)
operations. As you drag the entry for a tool, a square outline
pointer indicates the tentative position of the entry.
The tool box (if not already open, opens) blinks to indicate
the effect of the modification.
6. (Optional) — Repeat steps 4–6 for each additional tool
box you want to create or modify.
If you created any tool boxes, they are listed in the Tool
Boxes dialog box (Tools > Tool Boxes…). You can open
them using that dialog box.
The Customize dialog box lets you choose between a number

of techniques for manipulating the list box entries that
represent tools. The following procedures cover only the most
intuitive technique — “drag-and-drop.”

Tool Boxes
To select and open an existing tool box

for customization
1. From the Edit Tool Box combo box, choose the tool
box you want to customize.
The tools in the selected tool box are listed in the destination list
box in the order that corresponds to their slots in the tool box.
2. From the source list box, select the desired tool.
A triangle under the tool box name in the source list box indicates
that there are tools listed under the tool box name; double-clicking
displays the available tools. The tools are listed in the order
that corresponds to their slots in the tool box.
To restore a delivered tool box or tool frame

to its original state
1. From the Tools menu, choose Tool Boxes.
The Tool Boxes dialog box opens.
2. In the list box, select the desired tool box.
3. Click the Restore button.
4. Click the OK button.
To create and open a tool box or tool frame

1. From the Edit Tool Box or Edit Tool Frame combo box, choose
Create Tool Box or Create Tool Frame.
The Create Tool Box or Create Tool Frame dialog box opens.
2. In the Name field, key in a name for the new tool box; this is the
text that will appear in the title bar of the tool box.
In the Customize dialog box, the tool box name is automatically
chosen in the Edit Tool Box or Edit Tool Frame combo box.
This means the new tool box is ready to have tools (or child
tool boxes if it is a tool frame) inserted in it.

Tool Boxes
To import MicroStation Version 5 palettes

1. Create a new user interface.
See To create a new user interface component on page 1-11.
2. Exit MicroStation.
3. Locate your MicroStation version 5 modification resource files.
These files are stored in subdirectories whose name matches the
desired user interface. For example, if the user interface you use
is called “Roads,” there will be a subdirectory in the operating
system named “Roads”. By default these subdirectories are located
under the “Workspace\interfaces\MicroStation” directory.
4. From the operating system copy your MicroStation version 5
modification files into the subdirectory that corresponds with
the new interface name you create in step 1.
By default this subdirectory will be located under the
“Workspace\interfaces\MicroStation” directory.
5. Start your current version of MicroStation, and then select from
the MicroStation Manager dialog box Interface option menu
the new user interface you created in step 1.
6. Enter a design file as you normally would.
To import MicroStation Version 5 menus

1. Follow steps 1-5 for To import MicroStation Version 5
palettes (see page 4-6) .
The MicroStation Version 5 menu displays across the top of
the screen, replacing the MicroStation 95 menu.
2. Load customize to incorporate MicroStation 95 menu items using
Workspace > Customize if that portion of the menu is available
or
Use User > Workspace > Modify User Interface if the
Version 5.0 menu is available
or
Key in MDL LOAD CUSTOMIZ;CUSTOMIZ DIALOG if
neither of the previous options are available.

Tool Boxes
3. In the Customize dialog box, select the Menu bar tab.

The active menu appears in a list box on the right side
of the Customize dialog box and the Version 5.0 menu
appears on the left side in a list box.
4. Drag and drop the desired menu items.
To convert a custom palette created with

MicroStation Version 5.0 or earlier to a
tool box and open it
The Customize dialog box opens.
2. Select the Convert Palettes tab.
3. In the list box, select the name of the palette you want
to convert to a tool box.
4. Turn on the Convert to Tool Box check box. You can also
turn on the Delete Palette Resource check box if you want to
delete the original palette after converting it.
5. Click OK.
After processing, your custom tool boxes will be available
from the Tool Boxes dialog box.
The items in the Convert Palettes tab are identical to those in the
Convert Palettes dialog box (previously accessed by choosing Import
Custom Palette from the Tool Box option button). If no custom palettes
exist in the current user interface, the items are hidden and the “No
custom palettes exist in this interface” message displays.
If you customized one of MicroStation’s delivered palettes, importing

it will not replace the corresponding delivered tool box. If it did you
might accidentally eliminate enhancements and new functionality.
If you created a custom icon in Version 5.0, a tool tip and description is
generated for the icon. If the icon contains a MicroStation command,
the tool tip and description corresponding to that command is used. If

the icon contains a user-defined, key-in string, the tool tip reads the
User-defined tool and the description will be the key-in string.
While MicroStation supports palettes, including Version

5.0 custom palettes, this palette support does not include
docking, resizing, or tool tips.
To move a child tool box from one slot to another

1. In the destination list box (in the Customize dialog box), drag
the entry for the tool box to the desired slot.
The destination slot is determined by the position of the pointer
relative to other entries when you drop the entry (release the Data
button). If the pointer is in the top half of an entry, the destination
slot is directly above that entry; if the pointer is in the bottom half
of an entry, the destination slot is directly below that entry.
To delete a child tool box

1. Drag the destination list box entry for the tool off the list box.
or
Select the destination list box entry and click the Remove button.
Inserting child tool boxes
To insert a child tool box

1. In the Customize dialog box, select the Tool Boxes tab
and turn on List Tools By Tool Box.
The source list box lists all MicroStation and custom
tool boxes in alphabetical order.
2. Drag the entry for the tool from the source list box to the
desired slot in the destination list box.

Expanding menus
Expanding menus
To expand/contract the source (Available

Tools From) list box
1. Double-click anywhere in a highlight bar that contains
a triangle below the tool name.
A triangle indicates that there is a list that can roll up or down.
Rearranging tools
To move a tool from one slot to another

1. Drag the tool to the desired slot.
To delete a tool
1. Drag the destination list box entry for the tool off the list box.
or
Select the destination list box entry for the tool and
click the Remove button.
The above procedures also apply to view controls (see View

Control Bars on page 4-22).

Inserting tools
Inserting tools
To insert an existing tool

1. In the Customize dialog box, select the Tool Boxes tab and
turn on List Tools Alphabetically.
The source list box lists all MicroStationtools in alphabetical order.
Alternative method — To insert an existing tool

1. In the Customize tool box, select the Tool Boxes tab and
turn on List Tools By Tool Box.
The source list box lists all MicroStation and custom
tool boxes in alphabetical order.
2. Double-click the source list box entry for the tool box
that contains the desired tool.
The source list box lists the member tools immediately
below the list box entry for the tool box.
Only the drag-and-drop portion of the procedure applies to view controls.
The above procedure also applies to view controls (see View Control
Bars on page 4-22). (View controls cannot be modified, however.)
To create and insert a tool

1. In the destination list box, select the entry for the tool before
which you want to insert the new tool.
2. Click the Insert button.
The Insert Tool dialog box opens. In the drawing area, a
pixel grid is displayed as a drawing aid.

Inserting tools
Insert Tool
dialog box
3. In the dialog box’s Options menu, turn on Draw Both Icons.

4. Draw the tool icon using the graphical tools in the Tool
palette to the left of the drawing area.
5. In the Tool Tip field, key in the Tool Tip text for the tool.
6. In the Description field, key in the text for the tool’s
status bar description.
7. In the Key-in field, key in the action string to be associated
with the tool. If a multiple key-in action string is specified, the
key-ins must be separated by semicolons (;) — for example,
co=red;wt=2;lv=3;place smartline. For information about action
strings, see Action Strings on page 4-48.
8. To adjust the icon (foreground) color, choose the desired color
from the Options menu’s Icon Color submenu.
If you make a mistake while drawing the icon and want to start
over, click the Reset button in the Insert Tool dialog box.

Inserting tools
To use a drawing tool

1. Select a drawing tool from the Tool palette.
2. Position the pointer where you want to begin drawing.
3. Drag the pointer in any direction (while holding down the
Data button). This extends a line or shape, depending
on the tool you have selected.
4. Release the Data button when the object is displayed
with the size and shape you desire.
To move a contiguous section of the icon
1. Select the Selection tool from the Tool palette.
2. Drag a selection rectangle around the section you want to move.

3. Position the pointer in the selection rectangle.
4. Drag the section to its destination.
To clear (apply the background color to) a

contiguous section of the icon
1. Select the Selection tool from the Tool palette.
2. Drag a selection rectangle around the section you want to clear.

3. From the Edit menu, choose Clear.
To clear the entire pixel grid

1. From the Edit menu, choose Clear All.
or
Click the Reset button.

Modifying tools
Modifying tools
You can:
• Modify a tool’s icon (its graphical label). An icon is composed

of dots called pixels. Each icon has a small version (23×23
pixels) and a large version (31×31 pixels).
• Change the tool’s description (as it appears in the status
bar), tool tip text, or associated action string. A multiple
key-in action string can be specified.
By modifying existing tools, you can in effect create “power tools” —
tools that start multiple key-in action strings. For example, a “power
tool” for drawing electrical wiring might do the following:
ACTIVE COLOR=red;ACTIVE WEIGHT=2;ACTIVE

LEVEL=elec;PLACE SMARTLINE
This tool would set the Active Color to red, set the Active Line Weight
to 2, set the Active Level to elec(trical), and select the Place SmartLine
tool. You might want to modify the Tool Tip text to read “Place Wiring.”
General Procedure — To Modify a Tool

1. In the destination list box, select the entry for the tool
and click the Modify button.
or
In the destination list box, double-click the entry for the tool.
The Insert Tool dialog box opens. The drawing area contains a
magnified representation of the icon. A pixel grid is displayed
as a drawing aid. The tool’s Tool Tip text is shown in the
Tool Tip field. The tool’s status bar description is shown
in the Description field. The action string associated with
the tool is shown in the Key-in field.

Modifying tools
Insert Tool
dialog box
with tool icon
displayed
2. Use the controls in the dialog box to modify the tool.

To modify the icon (foreground) color, choose the desired color
from the Options menu’s Icon Color submenu.
To modify the tool icon, use the graphical tools in the
tool palette to the left of the drawing area. See To create
and insert a tool on page 4-10.
If the small version of the icon is in the drawing area and you want
to modify the large version, or vice-versa, click the corresponding
button, on which the icon is displayed at its actual size, to the left
of the drawing area. To modify both the small and large versions
at the same time, turn on Draw Both Icons in the Options menu.
To modify the Tool Tip text, key in the text in the Tool Tip field.
To modify the status bar description, key in the text
in the Description field.
To modify the action string associated with the tool, key in
the new action string in the Key-in field. If a multiple key-in
action string is specified, the key-ins must be separated

Pull-Down Menus
by semicolons (;) — for example, co=red;wt=2;lv=3;place

smartline. For information about action strings, see
Action Strings on page 4-48.
3. When done, click the OK button.
If you make a mistake while modifying the tool and want to start
over, click the Reset button in the Insert Tool dialog box.
Pull-Down Menus
The Customize dialog box (Workspace menu > Customize) is used
to customize the main menu bar and its member menus.
General Procedure — To Customize the

Main Menu Bar
2. From the tab menu, choose Menu Bar.
The source (Available Menus From) and destination (Edit
Menu Bar) list boxes show the names of the tools in
the menu bar. (The destination list box is used only for
inserting menus and menu items.)
Customize
dialog box
with the
Menu Bar tab
displayed

Pull-Down Menus
3. Double-clicking anywhere on a row with a menu or submenu

will expand/collapse the menu. It is not necessary to
click precisely on the arrow.
4. Make the desired modifications to the menu bar (repeat
step 3 as necessary).
Modification type
Rearranging menus (see
page 4-17)
Modifying menus (see page 4-18)
Inserting menus and menu
items (see page 4-21)
operations. As you drag the entry for a menu or
menu item, a rectangular outline pointer indicates the
tentative position of the entry.
The menu bar blinks to indicate the effect of the modification.
The Customize dialog box lets you choose between a number of

techniques for manipulating the list box entries that represent
menus and menu items. The following procedures cover only the
most intuitive technique — “drag-and-drop.”
Separator bars, the horizontal lines that serve as logical subdivisions

within menus, are themselves menu items. In the list boxes in the
Customize dialog box, a dot indicates a separator bar.
To restore the main menu bar to its “as

delivered” state
1. With the Customize dialog box open, key in CUSTOMIZ
RESTORE MENUBAR in the Key-in window.
An alert box opens to confirm the request.
2. Click the Yes button.

Rearranging menus
Rearranging menus
To move the location of a menu on the menu bar

1. In the source list box, drag the entry for the menu to the desired slot.
2. If you move a (top level) menu to a slot inside another menu,
the moved menu becomes a submenu.
To move a menu item to a different location in

the same menu or to a different menu
1. In the destination list box, drag the entry for the menu
item to the desired slot.
If you move a menu item with an attached submenu to a slot
directly before a (top level) menu, the submenu becomes a menu.
If you move a menu item with no submenu to a slot directly
before a (top level) menu, the item is inserted as the first
item in that menu. The remaining items are automatically
listed if they were not previously.
Some standard MicroStation menu items should not be moved to

other menus as they may no longer exhibit their unique behavior.
For example, if Undo is moved from the Edit menu, it will no longer
display the action that is eligible for negation (for example, Undo place
smartline). It will also always be enabled or disabled, as specified in the
Modify Menu Item dialog box, regardless of the state of the undo buffer.
To delete a menu from the menu bar

1. Drag the destination list box entry for the menu off the list box.
or
In the destination list box, select the entry for the menu
and click the Remove button.

Modifying menus
To delete a menu item

1. Drag the destination list box entry for the menu item off the list box.
or
In the destination list box, select the entry for the menu
item and click the Remove button.
If the menu item is a submenu, deleting the item also

deletes the submenu entries.
Modifying menus
You can:
• Modify a menu’s name.

• Modify a menu item’s name.
• Enable or disable a menu item.
• Attach or detach a submenu.
• Modify the action string associated with a menu item.
You can create menu items that start multiple key-in action
strings. For example, a menu item, Wiring, for drawing
electrical wiring might do the following:
ACTIVE COLOR=red;ACTIVE WEIGHT=2; ACTIVE

LEVEL=3;PLACE SMARTLINE
This menu item, would set the Active Color to red, set
the Active Line Weight to 2, set the Active Level to 3, and
select the Place SmartLine tool.
To modify a menu’s name

1. In the destination list box, select a menu item and then
click the Modify button to modify a menu name. This
is necessary since double-clicking the menu item name
expands the submenu if one exists.
The Modify Menu dialog box opens.

Modifying menus
Modify Menu
dialog box
2. In the Label field, type the new name. Insert the tilde character
(“~”) immediately before the character that will be the mnemonic
access character — for example, E~LEMENT for Element.
To modify a menu item

1. In the destination list box, double-click the entry for the item.
The Modify Menu Item dialog box opens.
Modify Menu
Item dialog
box
2. Use the controls in the Modify Menu Item dialog box to

make the desired modifications.
To modify the name, type the new name in the Label field.
Insert the tilde character (“~”) immediately before the character

Modifying menus
that will be the mnemonic access character — for example,

TEXT ~GLOSSARY for Text Glossary.
To enable or disable the item in the menu, turn Enabled on or off.
To modify the action string associated with the item, type the new
action string in the Key-in field. See Action Strings on page 4-48.
To attach a submenu to the item, turn on SubMenu Attached. To
detach a submenu from the item, turn off SubMenu Attached.
To assign or modify the keyboard accelerator, select Control
alone or with Alt or Shift to indicate the modifier key(s) and
type the accelerator key in the Accelerator field.
The following are important to remember when modifying a menu item.
• Any label that dynamically changes — for example, Show

Clipboard, Hide Clipboard — is always set by MicroStation. The
name of such an item can be changed, but the label may not reflect
the change when the menu bar is loaded for use.
• MicroStation controls the enabled state of some menu items

— for example, Cut, Copy, and Paste. The setting for such
an item can be changed, but the item may not reflect the
change when the menu bar is loaded for use.
To attach a tool box to a menu item

1. From the destination list box, expand the selection by
double-clicking on any menu.
2. Select an individual item and click on Insert… (or Modify…).
The Insert Menu Item dialog box opens.

Inserting menus and menu items
3. Click on Attach Tool Box….

The Select Tool Box dialog box opens.
Select Tool
Box dialog
box
4. Select the desired tool box and click OK to attach.
Inserting menus and menu items
To insert a new menu in the menu bar

1. In the destination list box, select the entry for the existing menu
before which you want to insert the new menu.
The Insert Menu dialog box opens.
Insert Menu
dialog box
3. In the Label field, type the menu name. Insert the tilde character
(“~”) immediately before the character that will be the mnemonic
access character — for example, E~LEMENT for Element.

View Control Bars
To insert a new menu item

1. In the destination list box, select the entry for the existing menu
item before which you want to insert the new menu item.
The Insert Menu Item dialog box opens.
Insert Menu
Item dialog
box
3. Use the controls in the Modify Menu Item dialog box.

Type the item name in the Label field. Insert the tilde
character (“~”) immediately before the character that will
be the mnemonic access character — for example, TEXT
~GLOSSARY for Text Glossary.
To enable or disable the item in the menu, turn Enabled on or off.
In the Key-in field, type the action string you want to associate
with the item. See Action Strings on page 4-48.
(Optional) To assign a keyboard accelerator, select Control
alone or with Alt or Shift to indicate the modifier key(s) and
type the accelerator key in the Accelerator field.
For more information about specifying menu items, see To

modify a menu item on page 4-19.
View Control Bars

The Customize dialog box (Workspace > Customize) is used to
customize the view control bars in view window borders. The

View Control Bars
default contents of the view control bars vary depending on

whether the active design file is 2D or 3D.
General Procedure — To Customize View

Control Bars
2. From the tab menu, choose View Border (if not already chosen).
Customize dialog
box with the
View Border tab
displayed
3. From the Edit View Border option menu, choose 2D View Border
(for 2D design files) or 3D View Border (for 3D design files).
4. Make the desired modifications to the view control bar.
Modification type
Rearranging view controls (see
Rearranging tools on page 4-9)
Inserting view controls (see Inserting
tools on page 4-10)
These modification procedures are simple “drag-and-drop”
operations. As you drag the entry for a view control, a square
outline pointer indicates the tentative position of the entry.

User Interface Settings

If the active design file has the same dimensionality (2D or 3D)
of the newly modified view control bar, the view control bars in
open windows blink to indicate the effect of the modification.
6. Repeat steps 3–5 to modify the other type of view
control bar (3D or 2D).
The Customize dialog box lets you choose between a number

of techniques for manipulating the list box entries that
represent tools. The following procedures cover only the most
intuitive technique — “drag-and-drop.”
To restore a view control bar(s) to its

“as delivered” state
1. With the Customize dialog box open, enter the appropriate
key-in in the Key-in window:
To restore Key in
View control CUSTOMIZ RESTORE VIEWTOOLS
bar — 2D 2D
designs
bar — 3D 3D
designs
bar — all BOTH
designs
An alert box opens to confirm the request.

This feature allows you assign an identifier to a set of modifications
to the user interface. This identifier behaves like a comment.

To save a set of customizations

2. From the tab menu, choose Interface Settings.
Customize dialog
box with the
Interface Settings
tab displayed
3. Enter a description for the User Interface Settings.

4. Click Save to store the description.
This description can be read in the About Workspace
window (Workspace menu > About Workspace) to the
right of the User Interface field.
About
Workspace
window

AccuDraw Keyboard Shortcuts
AccuDraw Keyboard Shortcuts

You can customize AccuDraw keyboard shortcuts using the
AccuDraw Shortcuts window.
To open the AccuDraw Shortcuts window

1. With the focus in the AccuDraw window, press the á?ñ key.
Alternative method — To open the AccuDraw

Shortcuts window
1. From the Settings menu, choose AccuDraw.
The AccuDraw Settings dialog box opens.
2. Click the Shortcut Key-ins button.
To edit a keyboard shortcut

1. In the list box, select the shortcut to edit.
2. In the AccuDraw Shortcuts window, click the Edit button.
The Edit Shortcut dialog box opens.
3. Make the desired changes — you can change the shortcut key,
the Description, or the MicroStation command entry.
To create a keyboard shortcut

1. In the AccuDraw Shortcuts window, click the New button.
The New Shortcut dialog box opens.

Function Key Menus
2. Key in the shortcut key, Description, and the MicroStation

key-in to be simulated.
AccuDraw keyboard shortcuts are stored in a text file so they can

be edited using any word processor or text editor as well as by
using the AccuDraw Shortcuts window. The configuration variable
AccuDraw Shortcuts (MS_ACCUDRAWKEYS) in the Operation
category of the Configuration Variables dialog box identifies the
name and location of the shortcuts file. In the “as delivered” Default
workspace, the configuration variable points to the file shortcut.txt
in Bentley’s “Workspace\system\data” directory.
Manually editing the shortcuts file is the only way to delete
a shortcut, identify a shortcut as 2D or 3D only, or rearrange
the ordering of the shortcuts.
Function Key Menus
A function key menu is a file that contains keyboard function

key definitions — assignments of actions to function keys.
Function key definitions are Action Strings (see page 4-48) as
in other types of user-definable menus.
The default function key menu in the Default workspace is funckey.mnu,

which is installed in Bentley’s “Workspace\interfaces\fkeys” directory.
The Function Keys dialog box (Workspace > Function Keys…)

is used to modify function key menus.
For a list of the function keys that are available on your system, see
“Function keys” in the Setup Guide. Definitions can also be created for
pressing the function keys along with the modifier keys áCtrlñ, áAltñ,
and áShiftñ. For information about how to press these modifier keys
on your system, see “Using the Keyboard” in the Setup Guide.
Creating function key definitions for function key combinations

that have special meaning in MicroStation, such as áF1ñ
(Help), is not recommended.

Function Key Menus
To modify function key definitions

1. From the Workspace menu, choose Function Keys….
The Function Keys dialog box opens. The title bar identifies
the open function key menu.
Function
Keys dialog
box
2. Select a function key in the list box.

or
In the Shortcut Keys section, turn on Ctrl, Alt, and/or Shift and
choose the desired function key from the Key option menu.
or
Press the desired function key and any modifiers.
3. Click the Edit button.
The Edit Key Definition dialog box opens.
Edit Key
Definition
dialog box

Digitizing Tablet Menus
4. In the New field, edit the definition. The definition must be

specified as an action string (see Action Strings on page 4-48).
If you select a previous key-in in the Key-in History list box,
that key-in replaces whatever text is in the New field.
5. (Optional) — To modify more function key definitions,
repeat steps 2–4.
6. (Optional) — To save the function key definitions in the

open function key menu, choose Save or Save As from the
dialog box’s File menu. If you choose Save, the open function
key menu is overwritten. If you choose Save As, the Save
Function Key As dialog box opens for creating a function
key menu with a different name or location.
7. In the Function Keys dialog box, click the OK button. If the

definitions were not saved (step 6), an alert box opens. If you do not
save the definitions at this point, they will remain in effect only for
the remainder of the session unless saved before the session ends.
Another function key menu can be opened from within a function

key menu. The action string must include the MicroStation
key-in for opening a function key menu: MENUATTACH MENU
<file_spec>, FK. This capability lets you create a series of related
function key menus that reference each other. (The alternate
key-in for ATTACH MENU is AM=.)
Digitizing Tablet Menus

You can use the following types of digitizing tablet menus
with MicroStation:
• Command menus contain menu blocks of varying shapes and sizes.
• Matrix menus contain menu blocks of a fixed size
organized in rows and columns.
• Cursor button menus assign actions to the tablet cursor
buttons that are not assigned as the Command, Data, 3D Data,
Reset, Tentative, or 3D Tentative buttons.
Command menus and matrix menus are sometimes collectively

referred to as “paper menus” because they exist in printed form. To

Types of digitizing tablet menus
use one you must attach it to the surface of the digitizing tablet (see
Attaching and activating tablet menus on page 4-31).
The tablet cursor button designated as the Command button (see

“Using the Mouse or Digitizing Tablet” in the Setup Guide) is used to
select a menu item in a menu block. You can attach a single command
menu and as many as three matrix menus to the tablet.
MicroStation is supplied with several Sample menus (see page 4-33)

that can be used as is or as a starting point for customization.
Types of digitizing tablet menus

These types of menus are used with digitizing tables or tablets:
• Cursor button menus are used to assign actions to the digitizing

tablet cursor buttons that are not assigned as the Command, Data,
3D Data, Reset, Tentative, or 3D Tentative buttons.
• Paper menus, attached to the surface of a digitizing table or tablet,
allow actions to be initiated by pressing the Command button
while the digitizing tablet cursor is pointing (on the tablet) to a
menu block. There are two types: Command and Matrix.
Command menus contain menu blocks of varying shapes and sizes
that can be located at any position on the menu.
Matrix menus contain menu blocks of a fixed size that are

organized in a matrix of rows and columns. Matrix menus
require less memory than command menus.

Attaching and activating tablet menus
Attaching and activating tablet menus

The ATTACH MENU (AM=) key-in is used to attach and
activate tablet menus.
To attach and activate a command menu

1. Tape the menu to the tablet surface.
2. In the Key-in window dialog box, key in AM=<menu>,cm.
MENU is the name of the menu.
3. Enter a data point to identify the menu origin at the
lower left corner of the menu.
4. Enter a data point on the upper right corner of the menu.
The message “Menu successfully attached” is displayed
in the status bar.
If the commands do not seem properly aligned on the tablet, delete

the file “mdgs.men” and reattach the menu.

Selecting menu items
To attach and activate a matrix menu

1. Tape the menu to the tablet surface.
2. In the Key-in window, key in AM=<menu>,m<#>.
MENU is the name of the menu, and # is a number in the range
1–3, indicating the first, second, or third matrix menu.
3. Enter a data point to identify the menu origin at the
lower left corner of the menu.
4. Enter a data point on the upper right corner of the menu.
The message “Menu successfully attached” is displayed
in the status bar.
To activate a cursor button menu

1. In the Key-in window, key in AM=<menu>,cb.
MENU is the name of the menu.
Selecting menu items

Before using a tablet menu, you must use the ATTACH MENU
(AM=) key-in to activate it (see Attaching and activating
tablet menus on page 4-31).
To select a tool or view control using a

command or matrix menu
1. Position the tablet cursor on the menu block for the
desired tool or view control.
2. Press the Command button.
To select a tool, view control, or key-in using

a cursor button menu
1. Press the cursor button to which the desired tool, view
control, or key-in is assigned.

Deactivating menus
Deactivating menus
The ATTACH MENU (AM=) key-in is used to deactivate tablet menus.
To deactivate the command menu

1. In the Key-in window, key in AM=,cm.
To deactivate a matrix menu

1. In the Key-in window, key in AM=,m<number>.
NUMBER is in the range 1–3, indicating the first,
second, or third matrix menu.
To deactivate a cursor button menu

1. In the Key-in window, key in AM=,cb.
Sample menus
The following tablet menus are supplied with MicroStation
in electronic form.
Name Type Description

50MENU command Comprehensive menu
designed for use with
MicroStation Version
5. This menu is
supplied in printed
form as well.
ARCHPA matrix Area and architectural
patterns arranged for
easy selection and
placement as cells
(see Using Cells (see
page 13-14) ).

Customization terminology
Name Type Description

CBMENU cursor button Designed to be used
with tablet cursors
whose buttons
are arranged in a
rectangular array.
GEOMPA matrix Geometric patterns
arranged for easy
selection and
placement as cells.
LINEPA matrix Linear patterns
arranged for easy
selection and
placement as cells.
MSPUCK cursor button Designed to be used
with tablet cursors
whose buttons are
arranged in a circular
array.
designed for use
with MicroStation
Version 4.
designed for use with
MicroStation 95.
Customization terminology
A menu block is an area in a command or a matrix menu that defines
a region that is selected to perform a specific task.
An action string defines the action that MicroStation performs when a

menu block is selected or a cursor button is pressed. The user command
that creates the menu prompts you to enter the action strings. These
user commands are in Bentley’s “Workspace\system\ucm” directory.

Customizing cursor button menus
Menu control information is specified using the MSCB, MSCM,

and MSMM user commands and is placed on level 63. Menu action
strings have a specific format and should not be modified using
tools other than Move and Delete Element.
Menu graphical information is the graphical representation of the

command or matrix menu, including the graphics associated with each
menu block. The menu graphical information consists of elements
that can be placed on any level other than 63. The menu graphical
information is plotted and attached to a digitizing tablet.
A menu cell is a cell that contains all of the menu control information
— the location, range, type, and function of all menu blocks
and cursor button assignments in a menu.
A menu design file is the design file in which the menu graphical
information is drawn and the menu control information is placed.
Menu cells are created from the information in the menu design file.
Before a cursor button or paper menu can be used, it must be

attached to a design file with the ATTACH MENU (AM=) key-in.
See Attaching and activating tablet menus on page 4-31.
Customizing cursor button menus

You can create your own cursor button menus, customize the ones
supplied with MicroStation, or purchase them from various vendors.
To create a cursor button menu

1. Create a 2D design file.
2. Activate the MSCB user command (“mscb.ucm”).
A text node with the characters FB,CB is dynamically displayed.
FB is a two-letter code that designates MicroStation as the
application that will interpret the menu. CB identifies the
menu cell as a cursor button menu cell.
3. Place the text node at any point in the design plane.
(The location is not important.)

Customizing command and matrix menus
4. Key in the action type (C, D, E, K, M, P, R, S, T, or U).

See Action types on page 4-48.
5. Key in the button number (3–8). Buttons 1 and 2 are reserved as
the 3D Data and 3D Tentative buttons and cannot be reassigned.
6. Key in the action string. See Action Strings on page 4-48.
7. Enter a data point to position the action string. (The
location is not important.)
8. Return to step 5 to assign an action string to another button.
The action type remains the same.
Reset to return to step 4 to change the action type.
Reset twice to exit MSCB.
9. Attach the cell library in which to store the menu cell
— for example, “msmenu.cel.”
10. Set the Active Level to 63.
11. Turn off all levels in the view except level 63.
12. Select (or place a fence around) all of the elements in the
menu and the text node placed in step 3.
13. Define the cell origin with the Define Cell Origin tool.
14. Create the menu cell. Designate the cell as a menu cell by choosing
Menu from the option menu in the Create New Cell dialog box.
See To create a cellin the Using Cells chapter of the User’s Guide.

You can create your own command and matrix menus, customize
the ones supplied with MicroStation (see To modify a command
menu on page 4-40 and To modify a matrix menu on page 4-40),
or purchase them from various vendors.
To create a command menu

2. From the Settings menu, choose Design File.
The Design File Settings dialog box opens.

3. From Category select Working Units.

4. Set the Master Units to inches (IN), Sub-Units to tenths (TN),
and Resolution to 10 TN per IN and 1000 positional units
per TN (IN:10:TN:1000). Click the OK button.
5. Draw the menu graphical information (menu blocks, shapes,
and other graphic and text elements that will appear on the
paper menu) on any level except level 63.
The graphical information represents the action(s) associated
with each menu block. For example, a menu block from
which the PLACE CIRCLE CENTER CONSTRAINED
key-in is activated could contain a picture of a circle or
the text “Place Circle by Center.”
6. Activate the MSCM user command (“mscm.ucm”). MSCM is
used to create the control information on level 63.
A text node with the characters FB,CM is dynamically displayed.
FB is a two-letter code that designates MicroStation as the
application that will interpret the menu. CM identifies the
menu cell as a command menu cell.
7. Place the text node anywhere in the design plane. (The
9. Enter a data point to define the lower left corner of a menu block.
10. Enter a data point to define the upper right corner
of the same menu block.
The action string is placed in the menu block. If text extends
outside the block, turn off Fast Font for the view after the control
information is placed. The text will then fit inside the menu block.
12. Return to step 9 to define another menu block.
Reset to return to step 8 and change the action type.
Reset twice to exit MSCM.

16. Select (or place a fence around) the menu and the text
node you placed in step 7.
17. Define the cell origin at the lower left corner of the menu (not the
lower left corner of the fence) with the Define Cell Origin tool.
In step 17, it is helpful to place a block on level 63 that

encloses the entire menu and then place the cell origin at
the lower left corner of this block.
To create a matrix menu

2. From the Settings menu, choose Design File.
The Design File Settings dialog box opens.
3. From Category select Working Units.
4. Set the Master Units to inches (IN), Sub-Units to tenths (TN),
and Resolution to 10 TN per IN and 1000 positional units
per TN (IN:10:TN:1000). Click the OK button.
5. Draw the menu graphical information (menu blocks, shapes,
and other graphic and text elements that appear on the
paper menu) on any level except level 63.
The graphical information represents the action(s) associated
with each menu block. For example, a menu block from
which the PLACE CIRCLE CENTER CONSTRAINED
key-in is activated could contain a picture of a circle or
the text “Place Circle by Center.”
All menu blocks must be the same size (height and width). To
create a “block” that appears to be larger, two menu blocks
can be assigned to the same action string.
6. Activate the MSMM user command (“msmm.ucm”). MSMM is
used to create the control information on level 63.

7. Key in the number of rows (horizontal) and columns

(vertical), separated by a comma.
The size limits are up to 1600 menu blocks and up
to 10,000 characters.
8. Enter a data point to define the lower left corner of the matrix menu.
9. Enter a data point to define the upper right corner
of the matrix menu.
10. Key in FB to designate MicroStation as the application
that will interpret the menu.
A text node that contains the characters FB,MM is dynamically
displayed. MM identifies the menu cell as a matrix menu cell.
11. Place the text node anywhere in the design plane. (The
13. Identify the menu block.
The row and column values followed by the action string are
placed in the menu block. If text extends outside the block, turn
off Fast Font for the view after the control information is placed.
The action string will then fit inside the menu block.
15. Return to step 13 to identify another menu block.
Reset to return to step 12 to change the action type.
Reset twice to exit MSMM.
19. Select (or place a fence around) the menu and the text
node that you placed in step 11.
20. Define the cell origin at the lower left of the menu (not the lower
left corner of the fence) with the Define Cell Origin tool.

To modify a command menu

1. Open the menu design file and turn level 63 off in the view.
2. Make the desired modifications to the menu graphical information.
3. Turn level 63 on in the view.
4. If necessary, delete menu control information that no
longer has associated menu blocks.
5. Activate the MSCM user command (“mscm.ucm”).
6. Make the appropriate changes to the menu control information
(see To create a command menu on page 4-36).
7. When prompted to “Enter Text Node Origin,” Reset to
skip the placement of the text node.
8. Select (or place a fence around) the menu cell and text node,
define the cell origin, and save the cell in the desired cell library
(see To create a command menu on page 4-36).
To modify a matrix menu

1. Open the menu design file and turn level 63 off in the view.
2. Make the desired changes to the menu graphical information.
Add rows or columns, if desired.
3. Turn level 63 on in the view.
4. If necessary, delete the menu control information that no
longer has associated menu blocks.
5. Activate the MSMM user command (“msmm.ucm”).
6. Make the appropriate changes to the menu control information
(see To create a matrix menu on page 4-38).
7. Key in the number of rows and columns, and identify the two
corners of the menu. (This must be done each time the UCM
is run.) If you are not adding rows or columns, Reset when
prompted to “Enter Text Node Origin” to skip placement of text
node. Otherwise, delete the old text node and replace it.
8. Select (or place a fence around) the menu cell and text node,
define the cell origin, and save the cell in the desired cell library
(see To create a matrix menu on page 4-38).

Tutorials
Tutorials
Tutorials are screen menus that resemble dialog boxes. They can
be used to solicit or display information or instructions. When
a tutorial is activated, it is displayed in a window. The servicing
application for a tutorial is typically a user command (UCM)..
These components of a tutorial are apparent to the user:
• Key entry (input/output) fields

• Output fields
• Graphic selection fields
Key entry fields are areas in a tutorial designated to accept keyboard

input from the tutorial user or text output from the servicing
application. Output fields are areas designated to receive text
output from the servicing application. Graphic selection fields
are rectangular areas that can be selected with a data point;
they are analogous to buttons in dialog boxes.
Tutorials are built using the MSTUT user command (“mstut.ucm”)

supplied with MicroStation.
You can customize MicroStation dialog boxes without using tutorials.
Tutorial execution
A tutorial is drawn in a MicroStation design file and defined
as a cell in a cell library.
When a tutorial is activated with the TUTORIAL (AT=)

key-in, the following occurs:
1 . The cell library specified by the Tutorial Cell Library configuration

variable (MS_TUTLIB) is searched for the tutorial cell,
followed by the attached cell library.
2 . The name of the new tutorial cell is stored in the

TCB variable TUTNAM.

Tutorial cell format
3 . The control information for the cell is invoked.
4 . If a tutorial was already active, it is deactivated. If the servicing

application for the previous tutorial and new tutorial are the
same, the application continues to execute without interruption.
Otherwise, the application that serviced the previous tutorial exits.
If the application was a UCM, it exits through the EXITUC label.
5 . The display information (on levels 1-62) is displayed in a window.
6 . The servicing application for the new tutorial activates,

if it is not already executing.
If a single UCM services two or more tutorials, the TCB variable

TUTNAM determines the active tutorial.
A tutorial can also be activated from another tutorial by selecting a

graphic selection field that invokes tutorial activation (action type D).
Tutorial cell format

The major components of the tutorial cell are the tutorial text node,
the control information, and the display information.
Tutorial text node

Each tutorial cell contains a text node on level 63 that consists
of two text strings. The first text string identifies the servicing
application for the tutorial. The second text string consists of the
single character “T” that identifies the cell as a tutorial cell.
Control information
The control information in a tutorial cell describes how the tutorial
inputs and outputs are to be handled. Control information is specified
as action strings that are placed in text elements on level 63.
The action string syntax for specifying a key entry field is I,<n>,<m>.
n is the maximum number of characters that can be input or

Tutorial drawing conventions
output to the field. m is the identifying number by which the

servicing application references the field.
When the tutorial is activated, the insertion cursor is automatically

positioned at the key entry field with the lowest number. Each time
the tutorial user presses áReturnñ, the cursor advances to the next
numbered field. The fields are in ascending order. An input field can
also be activated when the user enters a data point in it.
When the user enters text in a key entry field, MicroStation

notifies the servicing application.
The action string syntax for specifying an output field is

O,<n>,<m>. n is the maximum number of characters that can
be output to the field. m is the identifying number by which
the servicing application references the field.
Graphic selection fields can be specified by action types A, C,

D, E, K, M, P, R, S, T, and U. Action type A is an application
command that is processed in the servicing application. The
action string syntax for specifying an application command is
A,<n>. n is the number that the application uses to identify the
command. (The other action types and the syntax for using them
are described in Action Strings (see page 4-48) .)
Display information
The display information in a tutorial cell consists of graphic
elements that display when the tutorial is activated. Display
information cannot be placed on level 63.

When a tutorial cell is drawn in a design file, certain conventions
must be observed. These include the following:
• The design file must be 2D.

• Display information can be drawn on any level from 1 to
62 and can consist of any MicroStation element. However,
when a tutorial cell is added to a cell library, any nested

cells are automatically converted to groups (orphan cells) to

speed up tutorial display operations.
• To conform with the aspect ratio and resolution of the
screen, the tutorial cell must be drawn in an area that
is 640 ¥ 496 positional units.
• For some applications, it is helpful to conform the text size of
the input and output field labels to the hardware-generated
characters output by the system on which MicroStation is running.
To match the scale of the hardware-generated characters, the
text size should be eight positional units square.
• Control information must be placed on level 63.
To build a tutorial
1. Develop the servicing application, which is typically a UCM.
3. Draw the display information on levels 1-62.
4. Activate the MSTUT user command (“mstut.ucm”). The UCM
is used to create the control information on level 63.
5. The UCM prompts you for the needed information. You can
Reset back one step at a time and exit the UCM with a
final Reset. The prompts are as follows:
ENTER SERVICING To specify a UCM as the servicing

SOFTWARE NAME application, key in the filename of
the UCM. To specify MicroStation
as the servicing application, key in
FB. MicroStation can be the servicing
application if the tutorial will have
only graphic selection fields that
invoke command actions. If you are
modifying an existing tutorial, skip
the prompt by typing a space and
then pressing áReturnñ.

ENTER TEXT NODE This prompt appears if you keyed in

ORIGIN the filename of a UCM or FB at the
previous prompt. In response, enter
a data point to position the text node
origin. While the inclusion of the text
node within the tutorial cell is vital, its
location within the tutorial cell is not.
ENTER ACTION TYPE Key in the letter corresponding to the
(A,C,D,E,I,K,M,O,P,R,S, type of action you wish to add to the
T,U) tutorial. See Action types on page 4-48.
DEFINE LOWER LEFT If you responded to the ENTER ACTION
CORNER OR NEW TYPE prompt with an A, C, D, E, K,
ACTION TYPE M, P, R, S, T, or U (action types that
represent graphic selection fields),
you are prompted to define with a
data point the location of the lower
left corner of the rectangle that is to
be the graphic selection field. At this
prompt you can alternately choose to
key in a new action type.
DEFINE UPPER If you are defining a graphic selection
RIGHT CORNER field, this prompt appears. Enter a data
point to indicate the desired location.
ENTER WIDTH OF This prompt appears for key entry and
FIELD output fields. Key in the maximum
number of characters that can be in
the field. Valid field widths range
from 1 to 80 characters.
ENTER FIELD This prompt appears for key entry and
NUMBER output fields. Key in a number that
uniquely identifies the field. Do not
assign the same field number to more
than one field. Be aware that the field
number affects the insertion cursor
positioning for key entry fields. When
the tutorial is activated, the cursor is
initially positioned at the key entry
field with the lowest field number.
Subsequent presses of the áReturnñ key
move the cursor to the field with the
next ascending field number.

INPUT LOWER LEFT This prompt displays for key entry

FIELD CORNER and output fields. Enter a data point
to indicate the position of the lower
left corner of the field.
ENTER COMMAND For a primitive command (P) action type,
NAME key in the name of the desired primitive.
ENTER UC # OR For a UCM activation (U) action type,
NAME key in either a number (1 to 999)
representing a UCM index slot number
or the filename of a UCM. If a number
is keyed in, a U-type graphic selection
field is constructed in the tutorial. If
a filename is keyed in, a text element
is placed on level 63 consisting of
“T,UC=<file_name>” where file_name is
the name of the UCM file given.
ENTER CELL NAME For a cell placement (C or R) action
type, key in the cell name.
ENTER SYMBOL For a symbol placement (S) action type,
CHARACTER key in the character that identifies
the symbol to be placed.
ENTER DISPLAY For a tutorial activation (D) action type,
NAME key in the tutorial cell name of the
tutorial to be activated. It is possible to
activate one tutorial from another.
ENTER OPTION For an application command (A) action
NUMBER type, key in the command number.
Application command processing is
performed in the servicing application.
ENTER CHARACTERS For a non-terminated key-in (K),
terminated command key-in (T), entry
key-in (E), or message (M) action type,
key in the desired characters.
After all the prompts have been answered for an action,
MSTUT constructs and places the appropriate text element
on level 63. For a graphic selection field, the text element’s
selection range is set up to coincide with the rectangular
area that has been designated for it.
6. Continue to define actions until the tutorial is complete.

7. When all fields have been defined, select or fence the elements in
the tutorial, including the text node that identifies the servicing
application. Define the cell origin with the Define Cell Origin tool.
8. Attach the cell library in which you want to store the tutorial
cell — for example, “msmenu.cel.”
9. Create the tutorial cell. Designate the cell as a tutorial cell
by choosing Tutorial from the option menu in the Create
New Cell dialog box. See To create a cellin the Using
Cells chapter of the User’s Guide.
Once the selection range is set for a graphic selection field, neither
the field nor the text element associated with it can be manipulated
without the selection range being affected. Therefore, if modifications
need to be made to a graphic selection field, the entire field and
its associated text string should be deleted and placed again
to ensure that the element range is correct.
MSTUT error messages
The following error messages are possible when running

the MSTUT UCM:
Message Indicates that

INVALID ACTION MSTUT received a character that was
TYPE not a recognized action type character.
INVALID BLOCK An error was detected in the definition
of the rectangular area for a graphic
selection field. For example, the point
defined as the lower left corner was
located at a higher point or to the right of
the point defined as the top right corner.
WIDTH MUST BE A key entry or output field width that
LESS THAN 81 exceeds the maximum allowable width
of 80 characters was requested.

Action Strings
Action Strings
The actions MicroStation performs when you select a tool, choose a
menu item, press a function key, or select a menu block are defined by
the action string associated with that object. At first it is simplest to
think of an action string as a MicroStation key-in or series of key-ins.
For example, the action string associated with the Place SmartLine
tool is the key-in PLACE SMARTLINE. The true effect of selecting the
Place SmartLine tool is activation of the PLACE SMARTLINE key-in.
Action types
Several types of actions can be specified in action strings and associated
with tools, view controls, menu items, menu blocks, and function keys.
Note that some of the action types cannot be used in IGDS.
Action type Syntax Description

Command E,<key-in> Simulates a key-in. The
Entry Key-in1 key-in specified by a
command entry key-in
is always activated,
regardless of state
of the active key-in.
For example, suppose
that PLACE CIRCLE
RADIUS is the active
key-in and is prompting
for the radius. If the user
selects a menu block of
action type E that
activates the PLACE
LINE CONSTRAINED
key-in, then PLACE
LINE CONSTRAINED
becomes the active
key-in.
Primitive P,<primitive> Activates key-in by its
IGDS primitive name.

Action types
Action type Syntax Description

Terminated T,<key-in> Simulates a key-in.
Key-in A terminated key-in is
normally used to get data
requested by prompts,
such as the radius of a
circle, text, or an answer
to a yes-or-no question.
Unterminated K,<key-in> Keys in an unterminated
Key-in string of characters and
waits for the user to
finish the string.
Print Message1 M,<message> Prints a message in
one of the status bar
fields. The format for
the message is the same
as the MSG operator in
user commands.
Place Active C,<cellname> Sets the Active Cell to
Cell: absolute cellname and activates
the PLACE CELL
ABSOLUTE key-in.
Place Active R,<cellname> Sets the Active Cell to
Cell: relative cellname and activates
the PLACE CELL
RELATIVE key-in.
Tutorial D,<tutorial> Activates specified
tutorial (see Tutorials
on page 4-41).
User command U,<ucm_number> Activates user command
defined in the user
command index file
for <ucm_number>
(see Indexed UCMs
on page 9-4).

Action type options
1
This action type cannot be used in IGDS.
If no type specifier (a single character separated from the rest

of the string with a comma) exists, MicroStation assumes that
the action type is a command entry key-in (E).
For examples of action strings, examine a menu design file that is

installed in Bentley’s “Workspace\system\menus\dgn” directory, such
as “50menu.dgn,” or see Entering multiple action strings on page 4-50.
Action type options

These options can be used immediately following the E, T, or K action
types or anywhere in a multiple action string following a semicolon
(see Entering multiple action strings on page 4-50).
/<character> If there is a slash (/) in an action string,

MicroStation pauses for user input. If the
slash is followed by d, k, or no character,
MicroStation does the following:
• /d — waits for a data point.
• /k — waits for a key-in.
• No character — proceeds
after any input.
%<character> A percent (%) character in an action
string is identical to the slash, except
that MicroStation does not display
any of its normal prompts. This is
useful to display custom prompts from
a menu. The actions %d and %k work
analogously to /d and /k.
Entering multiple action strings

Each action string can contain several actions (separated
by semicolons).

For example, this action string places a blue two-inch

circle at a user-specified point:’co=blue;E,PLACE CIRCLE
RADIUS;T,2;M,cfPlace 2 Inch Circle;%d;null’
The actions are as follows:
Action Description
co=blue A command entry key-in (since no
type is specified) that sets the Active
Color to blue. MicroStation activates
the ACTIVE COLOR key-in even if it
currently expects a data key-in.
E,PLACE CIRCLE The MicroStation key-in PLACE
RADIUS CIRCLE RADIUS.
T,2 A terminated key-in that enters
a radius of 2.
M,cfPlace 2 Inch Circle Displays the message “Place 2 Inch
Circle” in the status bar.
%d Waits for a data point without displaying
the normal prompts (preserving the
prompt displayed by the previous action).
null After the circle is placed, executes
the NULL key-in so that no tool or
view control is selected.


Part II: Exchanging and Sharing Data
Exchanging Data with
Other Applications
This chapter covers exchanging data with other applications.
• General information that applies to data exchange is covered

in Design Data in Other File Formats (see page 5-1) , General
Data Exchange Information (see page 5-3) , and General
Data Exchange Procedures (see page 5-9) .
• Information that is specific to IGES File Exchange is covered

in IGES File Exchange (see page 5-14) .
• Information that is specific STEP AP File Exchange is covered in

STEP AP203/AP214 File Exchange (see page 5-47) .
• Mapping of AutoCAD commands to MicroStation commands is

covered in Alias Manager in the on-line documentation.
Information that is specific to DWG or DXF File Exchange is

covered in the File Portability/Translation Guide.
Design Data in Other File Formats

MicroStation can directly import and export AutoCAD binary
drawing files “DWG,” with no intermediate translation to
an interchange format required.
MicroStation can also import and export files of the following format(s):
• DXF (Drawing Interchange) — a file format created by Autodesk,

Inc. that you can use to exchange data between MicroStation
and many CAD and graphics applications. Since DWG and
DXF files have the same entities, they are converted exactly
the same way and the same settings are used for both. For
information that is specific to exchange with DWG or DXF,
see the File Portability/Translation Guide.
• IGES (Initial Graphics Exchange Specification) — a public domain,
ANSI standard, interchange file format that is intended as an
international standard for the exchange of product definition
data between different CAD/CAM systems. For information

Exchanging Data with Other Applications
Other Types of Data Exchange
that is specific to IGES translation, see IGES File Exchange on

page 5-14. For information about exporting IGES files that are
compliant with the CALS Class I or Class II specifications, see
Exporting CALS-compliant IGES files on page 5-29.
• ACIS SAT — a file format that converts ACIS SAT data into
(import) or from (export) a MicroStation design file.
• STEP AP203/AP214 — a file format that converts STEP AP203
and AP214 data into (import) or from (export) a MicroStation
design file. AP 203 conformance classes 2, 3, 4, 5, and 6 are
supported. Both DIS and IS versions of AP 203 are supported,
however DIS is supported for background compatibility only. For
information that is specific to STEP AP203/AP214 translation,
see STEP AP203/AP214 File Exchange on page 5-47 .
• VersaCAD 386 (import only) — a file format that translates
VersaCAD files into MicroStation readable files.
• VRML World (export only) — a file format that translates
MicroStation into VRML (Virtual Reality Modeling Language),
including placing interactive links between geometry in the
VRML world and other Internet locations or VRML worlds.
For information that is specific to VRML translation, see
VRML Publisher (see page 5-53) .
• CGM (Computer Graphics Metafile) — an ANSI standard for the
exchange of picture data between different graphics software
that is device- and environment-independent.
A number of third-party translators to various formats are

described in the Enterprise Developer catalog.1
Other Types of Data Exchange

MicroStation can output the following for use with other software
for publishing or image processing:
• Linework (wireframe) data can be plotted as PostScript or
HPGL graphics. For general information, see the User’s Guide
1 Bentley Enterprise Developer Program Members around the world offer products and services
that compliment Bentley engineering solutions. An online catalog, located on the World
Wide Web at http://www.bentley.com/developer/catalog.htm, has search capabilities to locate
these products and services by company name, product name, or application area.

General Data Exchange Information
chapter, Plotting and Printing. For more specific information,

see the Printing and Plotting Guide.
• Rendered images can be saved by choosing Image >
Save… from the Utilities menu.
• “Screen shots” of tool boxes and dialog boxes. See Screen
Capture on page 5-55.
MicroStation can also convert image files in a variety of

Supported Image Formats (see page 5-59) .
The system Clipboard, if one exists, can be used to exchange data with
other applications. See Clipboard Operations on page 5-62.
Finally, you can import the contents of a text file into a MicroStation
design. See Importing Text (see page 5-81) .
General Data Exchange Information

This section has information that is relevant to any data exchange
with another application or format.
For format-specific information, see the following sections.
Format For more Application1

information, see
DWG The File Portabil- “dwgin.ma”
and DXF ity/Translation “dwgout.ma”
Guide.

Basic terminology
Format For more Application1

information, see
IGES IGES File Exchange “igesin.ma”
on page 5-14 “igesout.ma”
Import IGES
File dialog boxin
the on-line
documentation
Export IGES
File dialog box
in the on-line
documentation
CGM Import CGM “cgmin.ma”
File dialog boxin “cgmout.ma”
the on-line
documentation
Export CGM
File dialog box
in the on-line
documentation
1 The MDL applications, supplied in MicroStation’s “mdlsys\asneeded”

directory, that perform import (in) and export (out).
Basic terminology
The following terms apply to file exchange in general:
Entity — The fundamental unit of data in a DWG, DXF, IGES, or CGM

file. In general, entities are the equivalent of design file elements.
Receiving application — Application into which a file exported

from MicroStation will be imported.
Sending application — Application that created a file that

is to be imported into MicroStation.
Product-definition data — Graphical information that describes a

design (for example, a mechanical part, architectural design, site plan,
map, and so on) in 2D or 3D, with real-world units and precision

Choosing which translation to use
sufficient to create or build the actual product or design. Design files,

DWG, DXF, and IGES files can store product-definition data.
Picture data — Graphical information that draws a picture.

Real-world units and 3D are not required, and while the precision
may be quite high, the information is usable only as an illustration.
The CGM format stores picture data.
Choosing which translation to use

The best translation to use depends on factors that are
unique to each translation, including:
• The sending application or receiving application.

• The type of data being translated.
• Whether you are converting product-definition data or picture data.
The best way to convert between MicroStation and AutoCAD is

to open and save DWG files directly — it is not necessary to use
an intermediate format, such as DXF or IGES.
The CGM format is not intended for the exchange of product-definition

data, as are IGES and DXF.
When exporting to a receiving application that supports intelligent

entities (for example, NURBS), IGES File Exchange (see page 5-14)
usually is better than DXF. IGES is a more “robust” than DXF; that is,
it supports a far wider range of entities. IGES also is a non-proprietary
format that does not favor one vendor’s application.
Preserving as much data as possible

Items in one system may not have exact equivalents in the other.
Also, items that are common to both systems may be expressed
differently. In these cases, the goal is to perform a translation
that preserves as much data as possible. How completely this is
achieved depends on a variety of factors.

Opening a 3D file
If you perform frequent translations, it helps to learn about the

MicroStation and the DWG, DXF, IGES, or CGM formats and to set
up your designs in a way that minimizes data loss. This chapter
has some suggestions for doing this. For more information on DWG
and DXF, see the File Portability/Translation Guide.
It is a good idea to test translation with small drawings. Use drawings

that contain the same type of data used in your project — preferably
ones that have examples of all of the types of data used.
The raster conversion utility supports all import image formats.
Opening a 3D file
To import a 3D drawing file interactively, the active design file
must be 3D. To open a 3D drawing file from the system command
line, the translation seed file must be 3D.
Certain IGES entities cannot be represented in 2D. Unless you are

certain that the IGES file is 2D, it is recommended that the active
design file be 3D when the IGES file is imported.
The CGM format does not support 3D.
Keeping units and measurements correct

When opening a DWG, DXF, or IGES file, be sure that the
design file into which you place the file has appropriate working
units for the type of data in the file.
• For information about setting working units when importing a

DWG or DXF file, see the File Portability/Translation Guide.
• For information about setting working units when importing an
IGES file, see Keeping coordinate units correct on page 5-24.
The CGM format does not store data in real-world units.

Using settings files
Using settings files

Import and export settings help make translation as accurate as
possible with as little loss of “intelligence” as possible. Once you know
how these should be set for your project, they can be saved in an import
or export settings file that stores all settings for a particular conversion
as they were when the settings file was created or last saved.
Settings Adjusted in Configuration Default file

for variable
DWG or DXF
Import DWG / DXF MS_DWGINSET “dwgin.sfi”
Import dialog
box
Export DWG / DXF MS_DWGOUTSET “dwgout.sfi”
Export dialog
box
IGES
Import Import IGES MS_IGESINSET “igesin.sfi”
File dialog box
Export Export IGES MS_IGESOUTSET “igesout.sfi”
File dialog box
CGM
Import Import CGM MS_CGMINSET “cgmin.sfi”
File dialog box
Export Export CGM MS_CGMOUTSET “cgmout.sfi”
File dialog box
For example, the import settings file for IGES Import is pointed to
by the MS_IGESINSET configuration variable. When you import an
IGES file, the settings are read from this file. If an IGES import
settings file does not exist, the default file “igesin.sfi” is created
in Bentley’s “Workspace\system\data” directory.
Using settings files helps to ensure consistent translations. It may

be useful to have a different import and export settings file for each
sending application, receiving application, client, or project.

Log file
To attach a settings file other than the default

1. From the File menu in the appropriate Import dialog box,
choose Attach from the Settings File submenu.
The Attach Settings File dialog box opens.
2. Select the appropriate settings file in the list box.
3. Click OK.
To save the current import or export settings

1. From the File menu in the appropriate Export dialog box,
choose Save from the Settings File submenu.
The settings are saved in the attached settings file.
To save a new import or export settings file

1. From the File menu in the appropriate Export dialog box,
choose Save As from the Settings File submenu.
The Save Settings File As dialog box opens.
2. Enter the filename and directory and click Save.
Log file
A log file is a text file in which translation statistics and
diagnostics — the messages that display in the status box as
a translation is in progress — are saved.
By default, the log file is saved with the same filename and directory
as the file being translated with the extension “.log.”
To specify an alternate log file

1. From the File menu in the appropriate Import or Export
dialog box, choose Log File.
The Log File dialog box opens.

Versions supported
2. Specify the filename and directory for the log file.

3. Click OK.
Versions supported
The following versions of each format can be converted:
Format Can import Can export

versions versions
CGM 1.0 1.0
IGES 2.0, 3.0, 4.0, or 5.0 4.0 or 5.0 fixed-length
fixed-length ASCII ASCII
For information about which versions of DWG or DXF are supported,

see the File Portability/Translation Guide.
General Data Exchange Procedures

This section has general procedures for opening (importing) and
saving (exporting) files in other formats.
Opening files in other formats

You can open DWG, DXF, IGES or CGM files in these ways:
• Directly by choosing Open from the File menu. The current

import settings control the conversion. The contents of the
opened file are placed in a new design file that is created
from the Default Translation Seed File.2
• Interactively by choosing DWG or DXF, IGES, or CGM from the
File menu’s Import submenu. You can adjust import settings
2 The Default Translation Seed File is set by the MS_TRANSEED configuration variable (for
information about configuration variables, see Configuration Variablespage 3-1).

before proceeding. The contents of the imported file are placed

in the active design file. This changes the design file.
• By issuing commands from the system prompt. On systems
that have a system prompt, you can automatically convert
multiple files to design files.
To directly open a file in another format

1. From the File menu, choose Open.
The Open Design File dialog box opens.
Open Design File

dialog box
2. From the List Files of Type option menu, choose AutoCAD

Drawing Files [*.dwg], AutoCAD ASCII DXF Files [*.dxf],
IGES Files [*.igs], or CGM Files [*.cgm].
3. Select the file to open and click OK.
The file opens.
If you selected DWG or DXF, IGES, or CGM from the File
menu’s Import submenu, a status box displays messages
which describe the translation’s progress, which are saved
in a Log file (see page 5-8) .
The contents of the opened file are placed in a new design file that
is created from the Default Translation Seed File. The Default
Translation Seed File is set by the MS_TRANSEED configuration

variable. (For information about configuration variables, see

Working With Configuration Variables on page 3-7).
The settings used the last time you opened a file of the selected
Type interactively (by choosing Import from the File menu) control
how entities are converted to elements in the design file. See To
interactively import a file in another format on page 5-11.
To interactively import a file in another format

1. Open the design file (or create a new design file) into which
the DWG, DXF, IGES, or CGM file is to be placed.3
2. From the File menu’s Import submenu, choose DWG
or DXF, IGES, or CGM.
The appropriate initial import dialog box opens.
3. Use the Files list box to select the filename and directory, or in the
Files field, key in the filename of the file to import.
The appropriate secondary import dialog box opens depending
on the format of the file being imported.
Type This dialog box opens

DWG or DXF DWG / DXF Import dialog box
IGES Import IGES File dialog box
CGM Import CGM File dialog box
5. (Optional) — Adjust the import settings.
6. Click the Open button.

The file is opened. Messages that describe the conversion’s
progress are displayed in the Status area and saved
in a Log file (see page 5-8) .
3 To interactively import a 3D DWG or DXF file, the active design file must be 3D.
Unless you are sure an IGES file is 2D, the active design file should be 3D (see
Opening a 3D file on page 5-6). Be sure the design file has appropriate working units
(see Keeping units and measurements correct on page 5-6).

Saving files in other formats

MicroStation lets you save a design file as a DWG, DXF, IGES
or CGM file in the following ways:
• Directly by choosing Save As from the File menu. The current

export settings control the conversion.
• Interactively by choosing DWG or DXF, IGES, or CGM from
the File menu’s Export submenu. This method lets you
adjust export settings before proceeding.
• By issuing commands from the system prompt on
systems that have one.
To directly save a design file in another format

1. From the File menu, choose Save As.
The Save Design As dialog box opens.
Save Design
As dialog box
2. From the List Files of Type option menu, choose AutoCAD

Drawing Files [*.dwg], AutoCAD ASCII DXF Files [*.dxf],
IGES Files [*.igs], or CGM Files [*.cgm].

3. (Optional) — In the Files field, key in a name for

the file to be exported.
By default, the file is saved with the same name as the design
file, but with the suffix “.dwg,” “.dxf,” “.igs,” or “.cgm.”
4. Click OK.
As the file is saved, you can monitor the status by reading
the messages displayed in the Status window.
The settings that were set the last time you saved a design file
as a DWG or DXF, IGES, or CGM file interactively (using the
File menu’s Import or Export item) control how elements in the
design file are converted to entities in the exported file.
To interactively export a design file to

another format
1. From the File menu’s Export submenu, choose a file format.
A dialog box opens.
2. (If exporting DWG or DXF) From the List Files of Type option
menu, choose AutoCAD DWG Drawing [*.dwg] (the default)
or AutoCAD DXF Drawing (Ascii) [*.dxf].
If you choose an item other than the default, the default
suffix for the new file in the Files field changes to be
consistent with the chosen file type. (The default filename
is the same as the design file.)
3. (Optional) — In the Files field, key in a name for
the file to be exported.
4. Click OK.
A dialog box opens which lets you adjust export settings
for the type of file you are exporting.
Type This dialog box opens

DWG or DWG / DXF Export dialog box
DXF
IGES Export IGES File dialog box
CGM Export CGM File dialog box

IGES File Exchange
5. Set the settings as desired.

6. Click the Export button.
IGES File Exchange

IGES is a public domain, neutral file format that is intended as an
international standard for the exchange of data between different
CAD/CAM systems. IGES is an ANSI standard maintained by the
IGES/PDES Organization (IPO), under the direction of the National
Institute of Standards and Technology (NIST). The National Computer
Graphics Association (NCGA) acts as the administrator of the standard.
You can export IGES files that are compliant with the CALS
Class I or Class II specifications. See Exporting CALS-compliant
IGES files on page 5-29 for more information.
JAMA-IS IGES Translator

JAMA-IS is a Japanese subset of IGES designed by JAMA (Japanese
Automotive Manufacturers Association). They restricted the
entity set to what is relevant to their purposes and put some
additional limitations on the remaining ones. This version of IGES
translator supports JAMA-IS v.1.04 standard.
For information about which IGES file versions can be opened or

saved, see Versions supported on page 5-9.
For an introduction to how IGES files can be imported and exported in

MicroStation, see General Data Exchange Procedures on page 5-9.
IGES supports many entity types, ranging in complexity from

simple lines to complex surfaces. MicroStation can “cleanly” import
a large subset of the IGES entities. See IGES to MicroStation
element conversions on page 5-33 for details about the conversion
of specific IGES entities to MicroStation elements.
Translating large files can require substantial amounts of memory.

RAM and space on the hard disk are used. The message Aborting

Import/Export IGES
due to memory allocation failure indicates the need to add more

memory or free up more hard disk space.
Import/Export IGES
The following sections discuss the way the Import/Export IGES
facility deals with MicroStation dimension elements.
Importing dimension elements

The Import IGES facility imports IGES dimension entities as
MicroStation dimension elements. To override this default, you
must exclude the MicroStation dimension element. This is done in
the Exclude MicroStation Elements dialog box (from the Import
IGES File dialog box, choose Settings menu > Exclude uStn
Elements…) by selecting Dimension in the Included Elements
list and clicking the Exclude button followed by the Done button.
As a result, the Import IGES process converts IGES dimension
entities into discrete MicroStation primitive elements (lines, text,
etc.) and creates a graphic group. This output is the same as
generated with Version 5.0 of MicroStation.
Exporting dimension elements

By default, the Export IGES facility exports MicroStation dimensions
as IGES dimension entities. To override this, the Break Dimensions
option must be selected in the IGES Export Settings dialog box (from
the Export IGES File dialog box, choose Settings menu > General…).
When the Break Dimensions option is selected, dimensions are

exported as their constituent elements (lines, text, etc.). This results
in the same output as generated with Version 5.0.
IGES entities
The fundamental unit of data in an IGES file is the entity.
There are two major categories of entities.

IGES file organization
• Geometry entities define physical shapes; including

points, curves, surfaces, solids, and relations (collections
of similarly structured entities).
• Non-geometry entities provide specific attributes or characteristics
for geometry entities. Non-geometry entities include view, drawing,
general note, dimension, property, and associativity entities.
Some entities have several forms, or further definitions of the entity
within the entity type. Each entity is represented by an entry in
the directory entry section and the parameter data section of the
IGES file (see IGES file organization on page 5-16).

MicroStation can import or export fixed-length ASCII IGES
files with 80 characters in each line.
This section is intended to provide introductory information about

IGES for MicroStation users. If you require more detailed information,
see Available references about IGES on page 5-47 for information
about obtaining documentation of the IGES standard.
Each IGES file has five sections; identified by the letter in
column 73 of each line (S, G, D, P, or T).
Start section
Contains a human-readable comment; that is, it is meant to be

read by humans rather than by computers.
By default, “This file was produced by MicroStation” is placed

in an exported IGES file’s start section.
If desired, a text file can be specified using the Start Section File
dialog box (from the Export IGES File dialog box, choose File >
Start Section File). For example, it might have information such as
notes to the receiving company. If a text file is specified, the text
is reformatted into standard IGES record format.

Global data section

Contains information — the sending application, author, organization,
drafting standard, measuring system, IGES version, and other data
— needed by the receiving application. Some of this information
is specified in the Export IGES File dialog box.
Directory entry section

Serves as an index to the IGES file; there is one directory entry
for each entity. A directory entry has 20 right-justified fields of 8
characters each in two consecutive lines that store information that
is applicable to every type of entity. Important fields include:
1. Entity type
2. Pointer to the parameter data for that entity
4. Line font pattern
5. Level
10. Line count from beginning of directory entry section
11. Entity type (same as field 1)
12. Line weight
13. Color
14. Number of fields in the parameter data entry for that entity
15. Form number
18. Entity label; IGESOUT writes the MicroStation
element type the entity was created from
20. Line count from beginning of directory entry
section (same as field 10)
Parameter data section

Contains geometric information that is specific to each type of entity
— such as the endpoints of a line entity, the center and radius of a
circle entity, or the text in a general note entity. Parameter data
entries have a different length depending on the element type.

Terminate section
One line long; must be the last line in the IGES file.
A sample design file and exported IGES file
The examples here show a design file “output.dgn,” settings set to the
defaults (except for global data as specified in the Export to IGES
File dialog box), and the exported IGES file “output.igs.”
The design file

“output.dgn”
has one line
and one text
element.
Export IGES
File dialog box

Issues that affect IGES import and export
The exported
IGES file
“output.igs.”
In the above image:
• The start section “S” contains the default message since

no start section file was specified.
• The global data section “G” has information needed by the
receiving application, including the sending application
(MicroStation), author, and organization.
• In the directory entry section “D,” note the entity numbers
in field 1 and 11 (110 and 212 for the line and general note,
respectively) and the pointers in field 2 to the corresponding
line in the parameter data section “P” for each entity,
and the labels in field 18 (“LINE” and “TEXT”) in which
the IGES export program puts the MicroStation element
type from which they were created.
• The parameter data section “P” has information that
is specific to the entity type.
• The terminate section “T” must be the last line in the IGES file.

This section covers issues that affect IGES import and export.

Converting subfigure names

IGES subfigures are similar to MicroStation cells. There is no
limit to the length of IGES subfigure names, while MicroStation
cell names are limited to six characters.
• When an IGES file is imported, a subfigure name is truncated to

its first six characters. If the name already exists in the design
file or attached cell library, the sixth character is replaced with
a “0.” This number is incremented until a unique name is found.
• When exporting to IGES, it may be desirable to replace cell
names with longer subfigure names to match the naming
conventions of the receiving application.
You can use the Cell Names dialog box to customize how
cell names are translated.
To customize how Choose

Subfigure names are Settings > Cell Names in the
translated to cell names Import IGES File dialog box
during import.
Cell names are translated to Settings menu > Cell
subfigure names during Names… in the Export
export. IGES File dialog box
Saving customized lists of conversions in an import and export

settings file is particularly helpful if you must frequently exchange
data between MicroStation and another system that supports
subfigure names longer than six characters.
To set how a subfigure name is converted

to a cell name
1. From the Settings menu in the Import IGES File dialog
box, choose Cell Names.
The Cell Names dialog box opens.

Cell Names
dialog box
2. In the Subfigure field, key in the subfigure name.

3. In the Cell Name field, key in the cell name to which to
convert the subfigure name.
4. Click the Add button.
Converting text
A MicroStation font is assigned a number from 0 to 255 in a font library.
The font library “igesfont.flb” has equivalents for the IGES standard
text fonts. The default mappings from the IGES standard text
fonts to the fonts in “igesfont.flb” are as follows:
Standard IGES Font MicroStation

(“igesfont.flb”)
1. Standard Block 0. Standard
2. LeRoy 3. Engineering
17. Century Schoolbook 2. Fancy
18. Helvetica 43. Low Res Filled
1001. Symbol Font 1 15. IGES Symbol Font 1
1002. Symbol Font 16. IGES Symbol Font 2
1003. Drafting Font 17. IGES Symbol Font 3

Any IGES font that is not explicitly mapped is translated

to MicroStation font 1 (Working).
To use the “igesfont.flb” font library, be sure the MS_FNTLB

configuration variable is pointing to it. For more information
about setting configuration variables, see Working With
Configuration Variablespage 3-7.
Due to the wide variety of font conventions in different applications,

getting a “perfect match” can be difficult. Each situation is
different; you must decide which font mappings work best for
your translation. The following are suggestions for making
font translation as accurate as possible:
• Limit font usage to one or two fonts that have a similar

appearance in each package.
• Use “simple” fonts rather than “fancy.”
Features that are supported by the sending application may not

be supported by MicroStation. For example, some applications
support text attributes such as bold; MicroStation does not
support bold as a text attribute.
To set how an IGES font is converted

to MicroStation
1. In the Import IGES File dialog box, choose Settings
menu > Text Fonts.
The Text Fonts dialog box opens.
2. Key in the IGES font number in the Min field.
or
Key in the minimum and maximum of a range of IGES
fonts in the Min and Max fields.
3. Key in the MicroStation font number in the uSTN field.

Converting line styles

The IGES specification includes six standard line styles and custom
line font patterns defined by line font definition entities (type 304).
Custom line styles are not supported by MicroStation. The line

font patterns of entities with custom line font patterns can be
mapped to any of the MicroStation line styles.
The default line font pattern to line style mappings for IGES import are:
IGES line font pattern MicroStation line style

0. Undefined 0. Solid (SOL)
1. Solid 0. Solid (SOL)
2. Dashed 5. Short-dashed (SHD)
3. Phantom 6. Dash double-dot (DADD)
4. Centerline 7. Long dash-short dash
(LDSD)
5. Dotted 1. Dotted (DOT)
The default line style to line font pattern mappings for IGES export are:
MicroStation line style IGES line font

0. Solid (SOL) 1. Solid
1. Dotted (DOT) 3. Phantom
2. Medium-dashed (MEDD) 2. Dashed
3. Long-dashed (LNGD) 2. Dashed
4. Dot-dashed (DOTD) 4. Centerline
5. Short-dashed (SHD) 2. Dashed
6. Dash double-dot (DADD) 3. Phantom
7. Long dash-short dash 4. Centerline
(LDSD)
Conversion between line styles and line font patterns can
be customized. For more information, see the following
sections in the on-line documentation:

Issues that affect IGES import
• For import — Import IGES File dialog box

• For export — Export IGES File dialog box

This section covers issues that you should be aware of
when importing IGES files.
Certain IGES entities cannot be represented in 2D. Unless you

are sure the IGES file is 2D, it is recommended that the active
design file be 3D when an IGES file is imported.
Keeping coordinate units correct

Suppose an architect wants to import an IGES file into a
design file where the master units are feet and sub-units are
inches. If the file units of the IGES file being imported are
inches, Translation Units should be set to sub-units so that the
working units in the design file are correct.
IGES has no equivalent for MicroStation sub-units.
Levels
An IGES file can have an unlimited number of levels, numbered
with any non-negative integer. A MicroStation design file can
have up to 63 levels, numbered 1-63.
By default, when an IGES file is imported:
• Entities on level 0 in the IGES file are put on level

1 in the design file.
• Entities on levels 1-63 in the IGES file are put on the
same level in the design file.
• Entities on levels greater than 63 in the IGES file are
mapped to levels in the design file using the formula:design
file level = 1 + IGES file level mod 63

“IGES level mod 63” means “the remainder from the IGES
level divided by 63 (integer division).”
Example:
By default, entities on levels 64 and 127 of the IGES file are put
on level 2 in the MicroStation design file; entities on levels 65 and
128 of the IGES file are put on level 3, and so on.
The conversion of levels from IGES files to design files can be

customized in the Levels dialog box, which is opened by choosing
Settings menu > Levels in the Import IGES File dialog box.
To set how IGES levels are converted

to MicroStation
1. In the Import IGES File dialog box, choose Settings > Levels.
The Levels dialog box opens.
Levels dialog box
2. Key in the IGES level number in the Min field.

or
Key in the minimum and maximum of a range of IGES
levels in the Min and Max fields.
3. Key in the MicroStation level number in the USTN field.

Drawing sheets and view visibility

A single IGES file can represent both the model (the actual geometry)
and one or more annotated drawing sheets that display the model from
different views. Drawing entities (type 404) specify a drawing sheet as
a collection of annotation entities and one or more views of the model.
MicroStation does not directly support drawing entities; however,

sheet files provide the same functionality. An IGES file with
drawing entities can be split into the following:
• A model file (design file with the model).

• One or more sheet files (design file with a reference
file attachment for each drawing view as well as any
annotation entities associated with the drawing entity)
that are created for each drawing entity.
IGES also has a capability called “views visible” that is not

directly supported by MicroStation:
• The display of an individual entity can be enabled or

disabled for different views through the views visible form
of the associativity instance entity (type 402, form 3). We
will call this attribute view visibility.
• The symbology (line font pattern, color, or line weight)
of an individual entity can be changed in different views
through the views visible, color, or line weight form of the
associativity instance entity (type 402, form 4). We will
call this attribute view symbology.
The Drawings option menu in the Import IGES File dialog box
controls how drawing entities, view visibility, and view symbology
are handled when an IGES file is imported.

Issues that affect IGES export
An example
of the IGES
drawing entity.
The geometry
of the part is
drawn just
once. The
drawing entity
defines the
multiple views
of the object so
that it can be
viewed from
different sides.
The annotations
and border are
also part of the
drawing entity.

This section covers issues that you should be aware of when
exporting a design file to IGES.
Excluding IGES entities

The breadth of the IGES specification makes it impractical
for any receiving application to correctly interpret every IGES
entity. It is usually desirable to exclude an entity that is not
supported by the receiving application.
If an IGES entity listed in Alternate entities for excluded IGES

entities (export) (see page 5-28) is excluded, the geometry it
represents is approximated with the corresponding alternate
entity type. In most cases the approximation is less compact
and “intelligent” than the entity it replaces.

If an entity is not listed in the table, its exclusion causes its

geometry to be omitted from the IGES file.
The Exclude IGES Entities dialog box lets you exclude IGES entities.
To open this dialog box, choose Settings menu > Exclude IGES
Entities… in the Export IGES File dialog box.
Examples include the following:
• If the general note entity (type 212) is excluded, text elements

are replaced with their stroked representation as copious
data entities (type 106). The text appears correctly in the
IGES file, but requires far more file space and is interpreted
as a series of vectors rather than as text.
• If the receiving application does not support NURBS,
they should be excluded.
Alternate entities for excluded IGES entities (export)
The table lists alternate entities for excluded IGES entities,

unless the alternate is excluded as well:
IGES Entity Alternate If Excluded

100. Circular Arc 126. Rational B-spline Curve
102. Composite Curve Individual component entities
104. Conic Arc 126. Rational B-spline Curve
106. Copious Data 110. Line(s)
108. Plane (Bounded) 230. Sectioned Area
116. Point 110. Line (zero length)
126. Rational B-spline Curve 106. Copious Data
128. Rational B-spline Surface 126. Rational B-spline
Curves (rule lines)
142. Curve On Surface B-spline Surface boundaries
are ignored

Exporting CALS-compliant IGES files
IGES Entity Alternate If Excluded

144. Trimmed Surface Grouped holes are exported
as Sectioned Area entities
(type 230)
212. General Note 106. Copious Data
230. Sectioned Area Bounding elements area
pattern
308. Subfigure Definition Individual component entities
314. Color Definition Standard colors are used
408. Singular Subfigure All cells are dropped (placed
Instance as individual entities in
the IGES file)
If an element does not appear in the table, its exclusion causes

its geometry to be omitted from the IGES file.

CALS is an acronym for the United States Department of Defense
Computer-aided Acquisition and Logistic Support initiative. The goal
of CALS is to integrate and standardize the digital data received
from Department of Defense suppliers. The CALS IGES specification
is a series of different classes of IGES files. Each class is a subset
of the IGES entity types, as specified in MIL-D-28000A.

CALS Class Settings For the Exchange

File of
I. 2D Technical “cals1.sfo” 2D figures and
Illustration illustrations
normally found
in technical
publications.
II. 3D Engineering “cals2.sfo” 3D engineering
Drawings drawings (export
settings are very
close to default IGES
export settings).
Settings files for CALS export
The “cals1.sfo” and “cals2.sfo” export settings files specify

export settings as follows.
Setting CALS Class I CALS Class II

“cals1.sfo” “cals2.sfo”
Start Section File “cals1.ssf” “cals2.ssf”
template for CALS template for CALS
Class I start Class II start
section section
Flattening On from the Top1 Off
Standard Colors On2 Off
3
Default Drawing On On
Excluded Entities All entities not No entities are
(see Settings in CALS Class I excluded.
> Exclude specification are
IGES Entities… excluded.
and IGES
Import/Export)

Setting CALS Class I CALS Class II

“cals1.sfo” “cals2.sfo”
Fonts (see All MicroStation All MicroStation
Settings > Text fonts are mapped fonts are mapped
Fonts… and IGES to IGES fonts 1, to IGES fonts 1,
Import/Export) 1001 and 1002 (the 1001, 1002, and
only fonts allowed 1003 (the only
in CALS Class I fonts allowed in
IGES files). CALS Class II
IGES files).
Level Placement All elements in Elements are
(see Settings the design file are left on the same
menu > Levels… placed on level 0 in levels as in the
and IGES the IGES file. design file.
Import/Export)
1
All entities in a CALS Class I file must be 2D. You can flatten in any
standard view. If Flattening is set to None and the design file is 3D, the
IGES file is not CALS Class I-compliant.
2 Custom color definitions are not allowed in CALS Class I IGES files.
3
CALS Class I and II IGES files must have at least one drawing entity.
Either “cals1.sfo” or “cals2.sfo” can be customized. Once you have

changed the export settings, in the Export IGES File dialog box, choose
File > Settings File > Save As… to save your changes.
To export CALS Class I-compliant IGES files

1. Attach the export settings file “cals1.sfo.” See To attach a settings
file other than the default on page 5-8 for a step-by-step procedure.
2. In the Export IGES File dialog box, fill in the Product Name field.
The product name is required in CALS Class I IGES files.
3. Using the Start Section dialog box, fill in the Start Section
information specific to your project.

All of the 2D entities

that are allowed in
CALS Class I IGES
files.
See Import IGES File dialog box for information about saving a
custom start section file for your project or organization.
To export CALS Class II-compliant IGES files

1. Attach the export settings file “cals2.sfo.” See To attach a settings
file other than the default for a step-by-step procedure.
2. In the Export IGES File dialog box, fill in the Author,
Organization, and Product Name fields. These are required
in CALS Class II IGES files.
3. Fill in the information specific to your project.

IGES to MicroStation element conversions
All of the 3D entities that are allowed in CALS Class II IGES files.

IGES entities (left) are converted to the related MicroStation elements
(right). Only supported IGES entities are listed.

IGES Entity MicroStation Element

100. Circular Arc 15. Ellipse
Closed arc 16. Arc
Arc
102. Composite Curve 14. Complex Chain
104. Conic Arc: 15. Ellipse
Closed arc 16. Arc
Arc
106. Copious Data:1 4. Line String, or 6. Shape,
Form 11, 12, 40, 63 or 14. Complex Shape
Form 20-21, 31-38 Line segments
108. Plane: bounded2 43
unbounded Shape, Ellipse, closed B-spline
Curve, or Complex Shape
Not supported
110. Line 3. Line
112. Parametric Spline Curve 27. B-spline Curve
114. Parametric Spline Surface 24. B-spline Surface
116. Point 3. Line (zero length)
118. Ruled Surface3 24. B-spline Surface
120. Surface of Revolution 24. Default is Surface of
Revolution; but, if ’surface
header’ is excluded (that is,
if the following is selected
in the Import IGES dialog
box: Settings > Exclude
uStn Elements), the entity is
translated into a B-spline
Surface
122. Tabulated Cylinder 24. B-spline Surface
124. Transformation Matrix Supported
126. Rational B-spline Curve 27. B-spline Curve
(all forms)
128. Rational B-spline Surface 24. B-spline Surface
(all forms)
130. Offset Curve 27. B-spline Curve


140. Offset Surface 24. B-spline Surface
142. Curve On A Parametric 27. B-spline Curve
Surface 24. B-spline Surface Boundary
Curve present
uv_curve present
144. Trimmed Parametric 25. Bounded B-spline Surface,
Surface4 if MicroStation Modeler is not
present; MicroStation Modeler
boundary representation, if
MicroStation Modeler is present.
150. Block 19. Solid (of projection)
152. Right Angular Wedge 19. Solid (of projection)
154. Right Circular Cylinder 23. Cylinder
156. Right Circular Cone 23. Cone
Frustum
158. Sphere 19. Solid (of revolution)
160. Torus 19. Solid (of revolution)
162. Solid Of Revolution 19. Solid (of revolution)
24. B-spline Surface (if
cross-section is a B-spline curve)
164. Solid Of Linear Extrusion 19. Solid (of projection)
24. B-spline Surface (if
cross-section is a B-spline curve)
202. Angular Dimension Angular Dimension, or primitive
elements (lines, text, etc.)5
206. Diameter Dimension Diameter Dimension, or
primitive elements (lines,
text, etc.)5
208. Flag Note Flag Note, or primitive elements
(lines, text, etc.)5
210. General Label General Label, or primitive
212. General Note — Forms 17. Text
0-8, 100-102, 105


214. Leader Leader, or primitive elements
(lines, text, etc.)5
216. Linear Dimension Linear Dimension, or primitive
218. Ordinate Dimension Ordinate Dimension, or
primitive elements (lines,
text, etc.)5
220. Point Dimension Primitive elements (lines,
text, etc.)
222. Radius Dimension Radius Dimension, or primitive
228. General Symbol General Symbol, or primitive
230. Sectioned Area5 Boundary elements enclosing
a hatch pattern.
308. Subfigure Definition6 1. Cell (in attached cell library)
34. Shared Cell Definition
312. Text Display Template Supported
314. Color Definition Supported
320. Network Subfigure 1. Cell (in attached cell library)
Definition6 34. Shared Cell Definition
402. Associativity Instance: Graphic Group
Form 1, 7, 9, 13, 14, 15, 16, 18 Supported (view visibility)
Form 3, 47
404. Drawing 8 Supported
406. Property Named level
Form 3. (level function) 36. Multi-line
Form 5. (line widening) Supported
Form 15. (name) View in sheet design file
Form 16. (drawing size) Units in sheet design file
Form 17. (drawing units)
408. Singular Subfigure 2. Cell (placed in attached
Instance6 cell library)
35. Shared Cell Instance
410. View 5. Saved View


412. Rectangular Array 2. Cell(s) (placed in a
Subfigure Instance6 rectangular array in attached
cell library)
35. Shared Cell Instance(s)
(placed in a rectangular array)
414. Circular Array Subfigure 2. Cell(s) (placed in a circular
Instance6 array in attached cell library)
35. Shared Cell Instance(s)
(placed in a circular array)
416. External Reference 5. Reference File
(Form 1)
420. Network Subfigure 2. Cell (in attached cell library)
Instance6 35. Shared Cell Instance
1 A MicroStation line string or shape element can have a maximum of 101 vertices.
If a copious data entity has more than 101 vertices, it is translated as a complex
chain or complex shape that contains multiple line strings.
2
Only bounded planes with a positive bounded area (form 1) are translated.
In this case, the bounding curve is interpreted as closed. For example,
if the bounding curve is a composite curve it is interpreted as a complex
shape rather than a complex chain.
3
Form 1 ruled surfaces are approximated as form 0. The parameterization of the
ruled surfaces is always taken from the rail curves as specified in form 0.
4
Trimmed parametric surface entities are translated to B-spline surface elements
with boundaries. Since MicroStation supports only polygonal surface boundaries,
curved boundaries are approximated by stroking the curves to polygons.
5
See Importing dimension elements on page 5-15.
6
The Subfigure Output control (IGES Import Settings dialog box) sets
how subfigures are translated. If no cell library is attached, Subfigure
Output is set to shared cells.
7 The Drawings control in the IGES Import Settings dialog box sets how view
visibility is handled. See also Drawing sheets and view visibility (see page 5-26) .
8 The Drawings control in the IGES Import Settings dialog box sets whether
drawing entities are ignored, merged into the design file, or have a
sheet file created with appropriate attached views. See also Drawing
sheets and view visibility (see page 5-26) .

MicroStation to IGES element conversions
MicroStation to IGES element conversions

MicroStation elements (left) are translated to the related IGES entities
(right) when the design file is exported, unless the IGES entity is
excluded (see Excluding IGES entities on page 5-27).
MicroStation Element IGES Entity

1. Cell Library Header 308. Subfigure Definition
2. Cell Headers 408. Subfigure Instance
3. Line 110. Line
4. Line String 106. Copious Data
5. Group Data Ignored
Saved View 410. View
Color Table 314. Color Definition
6. Shape 106. Copious Data
7. Text Node 212. General Note
11. Curve 126. Rational B-spline Curve
12. Complex Chain 102. Composite Curve
14. Complex Shape 144. Trimmed Surface
If bounded
15. Ellipse 100. Arc (Circles only)
104. Conic
16. Arc 100. Arc (Circular arcs
only) 104. Conic
17. Text 212. General Note
18. Surface of Revolution 120. Surface of Revolution
Surface of Projection 118. Ruled Surface
19. Solid of Revolution 128. Solid of Revolution
Solid of Projection 118. Ruled Surface
21. B-spline Pole Exported with B-spline Curve
or B-spline Surface header
22. Point String 116. Point(s)
23. Cone 128. Rational B-spline Surface

IGES translation errors and warnings
MicroStation Element IGES Entity

24. B-spline Surface Header 128. Rational B-spline Surface
If not bounded 144. Trimmed Surface
If bounded
25. B-spline Surface Boundary 142. Curve On A Parametric
Surface
26. B-spline Knot Exported with B-spline Curve
or B-spline Surface header
27. B-spline Curve 126. Rational B-spline Curve
28. B-spline Weight Factor Exported with B-spline Curve
or B-spline Surface Header
33. Dimension Dimension, or primitive
elements (line, text, etc.)1
34. Shared Cell Definition 308. Subfigure Definition
35. Shared Cell Instance 408. Subfigure Instance
36. Multi-linea Exported as primitive
components
37. Tag Text
66. MicroStation Application Ignored
87. Raster Header Ignored
88. Raster Data Ignored
1
See Exporting dimension elements on page 5-15.

Messages listed as errors are problems that cause import or export
to fail. Messages listed as warnings do not cause failure, but
indicate that the drawing may have lost some “intelligence” or
had some part omitted during translation.

Import and export errors

Message Meaning
Unable to open An error occurred opening the
output file design file you are importing the
IGES file into or the IGES file you
are attempting to export to; caused
by an invalid path specification,
the existence a write-protected file
with the same filename, or other
similar condition. (Command line
or batch method only)
Aborting due to Sufficient memory to complete
memory allocation the translation is not available.
failure Translating large files can require
substantial amounts of memory;
both RAM and hard disk space are
used. You must add more memory or
free up additional hard disk space.
Import errors
Message Meaning
Unable to open The specified IGES file does not
IGES file exist or cannot be opened.
Missing terminator The terminator section was not
section found at the end of the IGES
file. This usually indicates that
the specified file is not a valid
IGES file or is in some way
truncated or corrupted.
Invalid terminator The format of the IGES file’s
section terminator section is not valid.

Unable to create The design file could not be created

design file because the specified path does
not exist, an existing file with
that filename is write-protected,
or some other condition prevents
the creation of the specified
file. (Command line or batch
method only)
Unable to open The seed file specified by
seed file MS_DESIGNSEED does not
exist in the directory specified by
MS_SEEDFILES. (Command line
or batch method only)
Export error
Message Meaning
Unable to open The parameter data for the IGES
temporary file file is written to a temporary
file (iges.pds) during translation.
This file could not be created
for some reason.
Import and export warnings

Message Meaning
Unrecognized option An option was specified
that MicroStation could not
understand (command line or
batch method only).
Invalid option format The syntax of an option is
incorrect (command line or
batch method only).
Unable to open The indicated settings file does not
settings file exist or could not be opened.

Message Meaning
Settings version The version for the settings file
mismatch does not match the version of
MicroStation’s IGES translator.
Unable to create The specified path does not exist, a
settings file write-protected file with the same
filename exists, or the file cannot be
created for some other reason.
Unable to add An error occurred when updating
settings to file the settings file. This usually
indicates that the settings file
is write-protected.
Unable to open The specification file does not exist
specification file or could not be opened.
Import warnings
Message Meaning
Parameter type does The entity’s parameter data does
not match directory not match the type specified
record in its directory record. The
entity is ignored.
Invalid Copious A copious data (type 106) entity
Data Format of a form not supported by
MicroStation was encountered.
The entity is ignored.
Unsupported entity An entity type in the IGES file
is not supported and is therefore
omitted from the design file.
String constant These errors are caused by data
broken before that does not conform to the IGES
Hollerith character syntax specification. IGESIN
String field too attempts to infer or ignore the
long Hollerith invalid data. However, missing or
character missing incorrect geometry can result.
for string field No
field delimiter

Message Meaning
Invalid directory type These errors are caused by IGES
Invalid PDS Pointer files that are syntactically correct
in directory record yet contain data that is inconsistent
Invalid directory with the IGES specification. In most
sequence Invalid PDS cases IGESIN omits the erroneous
count in directory entities and continues translating.
record
Invalid line font An invalid line font was
(ignored) encountered. The default line
style is used for the entity.
Subfigure instance An error was encountered extracting
error the subfigure definition for the
specified instance. The instance is
omitted from the design file.
Unsupported conic An unsupported conic form
form was encountered. MicroStation
currently supports all of the
conic forms specified in the IGES
standard (ellipses, hyperbolas
and parabolas).
Invalid hyperbolic A degenerate hyperbola definition
conic was encountered. No geometry
is generated in the design file
for the conic entity.
Invalid parabolic A degenerate parabola definition
conic was encountered. No geometry
is generated in the design file
for the conic entity.
Unable to The conic cannot be reduced to
standardize conic standard form through standard
rotation and translation of axis
techniques. No geometry is
generated in the design file for
the conic entity.
Invalid revolution The axis for a surface of revolution
axis (type 120) was not a valid line
(type 110) entity. No geometry is
generated in the design file for
the surface of revolution.

Message Meaning
Invalid entity pointer An invalid entity pointer was
encountered in the parameter
data for the indicated entity.
The entity is ignored.
Invalid viewing The transformation for a view
transformation entity was not orthonormal. The
view definition is ignored.
Unable to create The specified sheet design file
sheet file: <filename> could not be created because the
specified path does not exist, a
write-protected file exists with the
same filename, or the file cannot
be created for some other reason.
The drawing entity associated
with this sheet is ignored.
Unable to open sheet The sheet seed file specified by the
seed: <filename> MS_SHEETSEED configuration
variable could not be opened
in the directory specified by
MS_SEEDFILES. Either the file
does not exist or read access is not
available. The sheet design file is
created by copying the header or
the model design file rather than
using the sheet seed file.
Invalid weight value An invalid line weight value was
encountered for the indicated
entity. The weight of the entity
is set to zero.
Subfigure The name of the IGES subfigure was
name changed: altered to meet the MicroStation
<Subfigure_Name> requirement of six character
=> <Cell_Name> alphanumeric cell names.
Can’t add cell to This error occurs if the active cell
library library is write-protected.

Message Meaning
Can’t find section A section pattern that is not in
pattern <CODEnn> the “igespats.cel” cell library was
encountered. The section pattern
is ignored. You can correct this by
creating a pattern cell for the section
and adding it to “igespats.cel” with
CODEnn as the cell name (nn is
the section code number).
Unable to open The pattern cell library
pattern cell library “igespats.cel” was not found. This
library is required for sectioned
area entities (type 230). The
configuration variable MS_CELL
is used to locate the cell library.
Be sure that “igespats.cel” exists
and that MS_CELL points to the
directory that it is in.
Unsupported An unsupported associativity form
Associativity Form was encountered. The associativity
entity is ignored.
Element off design The geometry for an IGES entity
plane is not included in the design plane
(volume in 3D) of the design file, and
is therefore omitted. This is usually
means that the working units of the
design file are not appropriate for
the IGES file being imported. This
can be corrected by choosing an
appropriate seed file, adjusting the
working units in the Working Units
dialog box, or setting Translation
Units to Sub-Units or Calculate.
Maximum cell MicroStation supports a maximum
size exceeded, cell size of 65,000 words (1 word
Subfigure dropped = 2 bytes). If an IGES subfigure
to components exceeds this limit, it is placed in the
design file as individual components
rather than as a cell or shared cell.

Message Meaning
No UV Curve in A type 142 (curve on surface)
Curve on Surface entity was encountered with zero
pointer for the UV curve entity.
The curve is ignored. This usually
causes a trim boundary to be
omitted from a surface.
Unsupported Line An invalid form for a Line Font
font definition (304) Definition entity was encountered.
form The font definition is ignored.
Export warnings
Message Meaning
Geometry omitted by Entities were omitted from the
exclusion of Entity: IGES file because the indicated
No./No. entities were excluded and there is
no alternate entity type to represent
it. This usually occurs only if the
copious data (type 106) or point
(type 116) entities are excluded.
Degenerate (zero MicroStation design files can
radius) arc omitted contain zero radius arc or circle
elements. The IGES specification
prohibits these entities and they are
therefore not exported to IGES.

Available references about IGES
Available references about IGES

IGES Version 5.2 National Computer Graphics
Association
2722 Merrilee Drive, Suite 200
Fairfax, VA 22031
(703) 698-9600 ext. 325
IGES 5.1 NIST
Recommended Bldg. 220, Room A127
Practices Guide Gaithersburg, MD 20899
(301) 975-3982
Parser/Verifier
Parser/Verifier is a utility that checks IGES files for conformance to
the IGES standard. It generates reports on entity usage and errors.
CALS conformance testing is optional. Parser/Verifier can greatly
speed the identification and resolution of IGES translation problems.
Parser/Verifier is available for PC, Intergraph Workstation, VAX/VMS,
Sun SPARC, and other platforms from IGES Data Analysis, 2001
North Janice Ave., Melrose Park, IL 60160; phone: (708) 344-1815; fax:
(708) 344-2840. Similar utilities may be available from other vendors.
STEP AP203/AP214 File Exchange

Application Protocols (APs) are used to exchange data. Each AP
pertains to a different application area. For example, AP227 pertains
to spatial plant technology and contains several entities pertaining
to that area such as pipe, elbows, etc. In addition, these APs also
use certain common entities known as generic resources, such as
geometry and topology, to define solid models.
AP203 applies to representation of mechanical parts and assemblies.

AP214 applies to representation of data relating to automotive
design. Present day AP203 files typically contains the boundary
representation model, assembly data, and limited amount of

Importing STEP data
other product information. AP214 files typically contain colors

and layers in addition to the generic resources.
The boundary representation of a model is the representation of a CAD

model by its boundary. For example, a surface model, consists of only
the surfaces use to make that model. Solid models include geometry
information (such as surfaces, curves, and points), and topology
information (such as edges, vertices, faces). While the geometry
information gives information about the form of the model, the
Topology information gives the connectivity between these geometric
elements, and the extent of the geometric elements.
STEP AP203 files are divided into different classes according to

what type of model they represent. For example, a surface model is
a Class 2 representation while a solid model is a Class 6.
Importing STEP data

This section describes how to import STEP data into MicroStation.
To import a STEP file

1. From the File menu, choose Import > STEP AP203/AP214.
The Import STEP AP203/AP214 File dialog box (a standard
file selection dialog box) opens.
2. Select the STEP file to be imported.
3. Click OK.
The (second) Import STEP AP203/AP214 File dialog box opens.

Importing STEP data
Import STEP
AP203/AP214
File dialog box
4. (Optional) — From the dialog box’s Settings menu,

choose Import Settings.
The AP203/AP214 Import Settings dialog box opens.
AP203/AP214
Import Settings
dialog box

Exporting STEP data
5. (Optional) — Make any necessary adjustments to the import

settings and click Done when you are finished.
6. In the Import STEP AP203/AP214 File dialog box, click

Import to start the translation process.
Status messages flash briefly in the Status area. If a logging
is enabled, these status messages are recorded in a log file.
When the process is complete, the translated model is shown
in a fitted view in the currently visible windows.
For an assembly, a single master part node is displayed at the

minimum x, y, and z extents of the translated model.
Exporting STEP data

This section describes how to export STEP data from MicroStation.
To export STEP data

1. From the File menu, choose Export > STEP AP203/AP214.
2. Identify the solid model or assembly to export and Accept.
The Export STEP AP203/AP214 File dialog box opens.
Export STEP
AP203/AP214
File dialog
box

Exporting STEP data
3. (Optional) — Key in the appropriate information in the Author,

Organization, and Approved By fields.
4. (Optional) — From the dialog box’s File menu, choose Export

As to specify an export file name.
If you do not perform this step, the name of the exported STEP file
is the same as that of the design file, with the extension .stp.
5. (Optional) — From the dialog box’s File menu, choose Log

File to specify a file name for the log file.
If you do not perform this step, the log file created is named the
same as the design file, but with the extension .log.
6. (Optional) — From the dialog box’s Settings menu,

choose Export Settings.
The AP203/AP214 Export Settings dialog box opens.
AP203/AP214
Export
Settings
dialog box
7. (Optional) — Use the dialog box controls to adjust the settings,

and click Done when you are finished.
8. In the Export STEP AP203/AP214 File dialog box, click

Export to start exporting data.
The dialog box closes when the export is complete.

Boundary representation data exchange and healing
Boundary representation data exchange and healing

The data exchange of boundary representation models requires
some level of approximation and repair, especially when compared
to the exchange of simple geometry. Two factors contributing
to the difficulty of translation are the additional connectivity
information present in the model and the different system level
interpretations with respect to model validity.
For example, in a boundary representation model, vertices must lie on

the edges they are supposed to lie on. In terms of an engineering model
system, for example, this means that the point representing a vertex
lies within a distance of 0.001 units from the curve representing the
edge. However, when this file is exported and then re-imported into a
target system, the target system may assume that a vertex lies on an
edge only if the point representing the vertex lies within a distance
of 0.0000001 units from the curve representing the edge.
Because of the different system tolerances, the model considered

valid in the exporting system is no longer considered as valid in
the importing system. Also, geometry considered valid in the
exporting system may be considered invalid in the importing
system. Due to these reasons, exchange of boundary representation
models is in general not a completely successful process. Healing
of the imported model is necessary so that it can be used in
downstream operations in the importing system.
Notes regarding Step AP203/AP214 translation

• When the Master units in the design file are different from
the units in the STEP file, the dimensions of the STEP model
are changed to the design file master units.
• Translation of solids, wires, sheets, surfaces, faceted
Preps, and curves is supported.
• For AP214 translation, there is also a bi-directional
exchange of colors and layers.

VRML Publisher
VRML Publisher
VRML Publisher provides translation of MicroStation geometry
to VRML (Virtual Reality Modeling Language), including placing
interactive links between geometry in the VRML world and other
Internet locations or VRML worlds. This enables you to publish
truly interactive worlds, rather than just static geometry.
VRML Publisher includes the following features:
• Linking geometry to Internet URLs through VRML

“WWWAnchor” node
• Automatic collection and optimization of image files
• Material and cell instancing
• Reduced VRML file size
As well as support for:
• Texture mapping
• Netscape’s Live3D Extensions (headlight, background
color, background image, etc.)
• Exporting text as VRML ASCII text nodes
• Exporting saved views as VRML cameras (viewpoints)
• Exporting MicroStation Modeler solids directly (without
converting to surfaces manually)
• Exporting VRML worlds
To export a view to a VRML world file

1. From the File menu, choose Export > VRML World….
2. Enter a data point to select a view to export.
The Export VRML World File dialog box opens.

Viewing VRML worlds
3. Adjust any settings necessary and click Export.

The Export VRML World dialog box opens for you to
save the VRML World file to a location. By default the
file is given the same name as the active design file plus
the .wrl extension. The default destination location is
“\Bentley\Workspace\projects\examples\generic\out”.
4. Click OK.
If some curved surfaces do not appear in your exported file, try

turning off Export Surface Normals and export again.
Viewing VRML worlds

To view and interact with a VRML world, some type of VRML browser
is required. A wide variety of browsers may be downloaded from the
Internet. For example, Netscape’s Live3D does an exceptional job of
handling large VRML worlds, although other browsers that completely
implement the VRML 1.0 specification should also work.

VRML exporting and viewing hints
VRML exporting and viewing hints

• Using cells (either normal or shared) can greatly reduce the size of
VRML worlds. This enables you to use many cells that require
only one stored definition but have multiple references to it.
• Create MicroStation saved views to represent significant views.
MicroStation’s saved views are exported as named camera
entities which most browsers support as “viewpoints.”
• Most browsers work best with perspective cameras. Turn the
camera on in saved views and, if possible, the view that is exported.
• Large VRML files are viewed efficiently only on powerful
computers and may also require a long time to download.
Reduce the file size by minimizing the use of curved surfaces
and the amount of geometry in general. Wherever possible,
use pattern maps rather than actual geometry.
Screen Capture
The Screen Capture utility (scrncapt.ma) is used to make a “screen
shot” of all or part of a MicroStation screen and save it in a
specified file format. It is designed to take snapshots of items in
MicroStation’s or an MDL application’s graphical user interface
— such as tool boxes, dialog boxes, and pull-down menus — for
use in documentation or training manuals.
Screen Capture captures an image at the resolution of the
monitor being used, exactly as it appears on screen, except
that the screen pointer is not shown.
Keep these considerations in mind:
• Use of certain word processing or page layout software with

certain printers may not produce a high quality printed image
of greyscale information in a screen shot.
• In many screen shots, elements suffer a loss of detail. To reproduce
detailed linework, it is usually best to plot the view as an
Encapsulated PostScript (EPS) or HPGL plotfile, depending upon
which format works best with your software and hardware.
• The quality of rendered images captured using Screen
Capture is limited by the resolution and the number of colors
your monitor supports. Choosing Image > Save… from the

Screen Capture
Utilities menu lets you create 24-bit files at any resolution

you care to specify, regardless of your display hardware.
This makes a much higher quality printed image possible if
a high resolution output device is used.
General Procedure — To Capture Part

or All of a Screen
1. Configure part or all of the display as it is to appear
in the screen shot.
2. Key in MDL LOAD SCRNCAPT. (This is recommended
to capture the entire display.)
3. Specify the part of the screen to capture.
To capture (see Key-in Button in

for details) dialog box
To capture the entire CAPTURE SCREEN Capture Screen
screen (see page 5-58)
To capture a CAPTURE Capture
rectangular area RECTANGLE Rectangle
inside a view (see
page 5-58)
To capture a view’s CAPTURE VIEW Capture View
contents (see page CONTENTS
5-58)
To capture a view’s CAPTURE VIEW Capture View
contents and border WINDOW Window
(see page 5-58)
To capture the CAPTURE SCREEN7 None
entire screen with
a pull-down menu
(see page 5-59)
To capture the CAPTURE FOCUS7 None
window that has
the input focus (see
page 5-59)
7
Must first be assigned to a function key.

Screen Capture
4. Follow the prompts in the status bar, which will vary

depending on the action taken in step 3.
The Capture Screen Output dialog box opens.
Capture
Screen
Output
dialog box
5. From the Format Type option menu, choose the

desired output format.
If you choose an item other than the default, the default
suffix for the image file in the Files field changes to be
consistent with the chosen file type.
6. If applicable, choose the compression level for the screen
capture from the Compression option menu (see Supported
Image Formats on page 5-59).
7. If the selected format supports more than one mode, choose
the desired mode from the Mode option menu (see Supported
Image Formats on page 5-59).
8. In the Files field, key in a name for the image file.
While the image is saved, an animated character
appears in the status bar.

Screen Capture
To capture the entire screen

1. In the Screen Capture dialog box, click the Capture Screen
button or key in CAPTURE SCREEN.
The pointer determines which screen is captured if more than one
monitor is used, but is not included in the image captured.
If CAPTURE SCREEN is assigned to a function key, it can be

activated by pressing the function key to which it is assigned.
This is useful to document the exact state of MicroStation during
a particular operation, and is the only way to make screen shots
of pull-down menus and modal dialog boxes. The same technique
can be used to capture the window that has the input focus with
the CAPTURE FOCUS key-in. To assign key-ins to function keys,
choose Function Keys… from the Workspace menu.
To capture a rectangular area inside a view

1. In the Screen Capture dialog box, click the Capture Rectangle
button or key in CAPTURE RECTANGLE.
2. Enter a data point to define one corner of the area.
3. Enter a data point to define the other corner of the area. It
must be entered in the same view as the first.
To capture a view’s contents

1. In the Screen Capture dialog box, click the Capture View
button or key in CAPTURE VIEW CONTENTS.
2. Select the view to capture.
To capture a view’s contents and border

1. In the Screen Capture dialog box, click the Capture View Window
button or key in CAPTURE VIEW WINDOW.
2. Select the view to capture.

Supported Image Formats
To capture the entire screen with a

pull-down menu
1. Post the menu.
2. Press the function key defined as CAPTURE SCREEN.
To capture the window that has the input focus

1. Press the function key that is defined as CAPTURE FOCUS.

These formats are supported for displaying images, importing images,
attaching reference raster files, saving images, or Screen Capture.
Format Ext Commonly used for Bits1 Compres-
sion
Img (X .p X-Windows palette 8 None
Window) format
Img (24 Bit) .a X-Windows RGB 24 None
format
Ingr. .cit Engineering 1 CCITT-G4
(Intergraph) drawings — highly
CIT compressed format
for large drawings
Ingr. .cot Monochrome or 8 None
(Intergraph) continuous tone
COT (greyscale) images;
color trained
Ingr. .rgb Full-color images 24 Variable
(Intergraph)
RGB


sion
Ingr. .rle Old standard 1 Run-length
(Intergraph) for engineering
RLE drawings. Uses
one-dimensional
run-length
compression. Prefer
“.cit” over “.rle” for
binary images.
JPEG (JFIF) .jpg Joint Photographic 8 or JPEG
Experts Group 24
— used for
greyscale or color
photographs. Very
high compression
rates, but “lossy”
compression.
Requires careful use.
PCX .pcx Popular PC format 1, 8, Run-length
supporting binary, or
mapped and true 24
color. Developed
by ZSoft for PC
Paintbrush.
PICT2 .pct Popular Apple 8 or Run-length
3
Macintosh format 24
4
PostScript5 .eps Encapsulated

PostScript
specification by
Adobe Systems, Inc.
Sun Raster .rs Sun-compatible 8 Run-length
format

MicroStation Field format (GRD) support

sion
Targa .tga Popular PC format 8, Uncom-
supporting binary, 16, pressed and
mapped, pseudo or 24, run-length
true color. TGA or
and TARGA are 32
trademarks of
Truevision, Inc.
TIFF6 .tif Tag Image File Any Various
7
Format; popular for
desktop publishing
Windows .bmp Microsoft Windows 8 or None
BMP bitmap 24
WordPerfect .wpg WordPerfect bitmap 8 Run-length
(WPG)8 format
1
Per pixel.
2 Output only — cannot be imported, displayed, or attached as a raster reference file.
3
The 24-bit PICT output produced by MicroStation uses direct RGB PixMaps
(described in Inside the Macintosh VI). To use these PICTs on the Macintosh, you
must have either System 7.0 or 32-bit QuickDraw version 1.2 under System 6.0.x.
4 If a PICT file produced by MicroStation takes too long to print from a

Macintosh, display the file on the screen at 100% scale and use a screen
capture utility to recapture the screen.
5
Not recommended for raster output, unless there is no other choice, since
the files are very large and difficult to edit.
6
MicroStation can import, display, or attach as a raster reference file either
compressed or uncompressed TIFF files. When creating an image, choose
TIFF (Compressed) to create a compressed TIFF, which is recommended
if the receiving application can handle compressed TIFFs.
7
Often used as a “wrapper” for other formats such as CCITT-Group 4 Fax.
8 Output only — cannot be imported, displayed, or attached as a raster reference file.
MicroStation Field format (GRD) support

The GRD file format used by MicroStation Field is supported.
To import a GRD file, from the File menu choose Import >

Setting the number of colors in exported images
GRD…. To export the active design file to a GRD format file,

from the File menu choose Export > GRD….
Setting the number of colors in exported images

The Mode setting controls the number of colors in exported
images. The available Modes depend on the Format. For example,
Intergraph RGB files must be 24-bit color, while PICT files can
be 24-bit color, 256 colors, or grey scale.
Unless the image is used with a display that supports 24-bit color or is
printed in color, using either 256 color or grey scale mode saves time
and results in smaller image files with no loss of quality, especially if
the final output is monochrome (for example, this guide).
Clipboard Operations
You can use the Clipboard in the Microsoft Windows environment
to exchange data with other applications.
Copying to the Windows Clipboard

In Windows, you can select text, bitmapped graphics, and metafiles
to be copied, or cut and copied to the Clipboard.
To copy elements to the Clipboard

1. With the Element Selection tool, select the desired elements.
2. From the Edit menu, choose Copy or Cut.
The selected elements are copied to the Clipboard.
Elements selected in MicroStation can be placed in the
Windows Clipboard in several formats:

Pasting from the Clipboard
• MicroStation Elements — This format is only recognized

by MicroStation and is used if the elements are pasted
back into the design.
• Windows Metafile — This format can be used to paste
vectors into other applications.
• Text — This format is used only if a text element is selected.

In Windows, the formats available in the Clipboard depend on the
application from which the data was copied. You can paste text,
bitmapped graphics, audio notes, and animation sequences in a
design file. You can also paste text into the Key-in window.
Dynamic Data Exchange (DDE) links
Text, audio notes, and animation sequences can be pasted in

a design file with DDE links. A linked item is automatically
updated in the design file when the originating file is changed
in the source (or server) application.
• If text is pasted with a DDE link, when both the source

application (for example, a word processor or spreadsheet)
and MicroStation are running, changing the object
in the source application causes the linked object in
MicroStation to automatically change.
• When an audio note’s icon is clicked in the design, the
sound file to which it is linked is played.
• When an animation sequence’s icon is clicked in the design,
the file to which it is linked is played.
To play pasted audio notes, you must have appropriate sound

drivers installed in Windows.
MicroStation identifies linked objects by filename. If an object has not

been saved as a file when it is pasted in a design, MicroStation may
not be able to locate it later. For example, if you create text in an
“untitled” document and do not “save as” before you paste the text,
MicroStation will not know where to find the linked text.

When you paste an object with a DDE link, if MicroStation

displays an alert box with the message “MicroStation requested
server is not responding,” make sure that:
• All source applications are located in the proper directories.

• The directories in which the server applications are found are
included in the system PATH environment variable.
To paste elements, text, or linked text

from the Clipboard
1. Copy items to the Clipboard from any application.
2. Go back to MicroStation.
3. If you want MicroStation to paste the information in the most
appropriate display format, from the Edit menu, choose Paste.
MicroStation dynamically displays the data from the Clipboard.
If multiple formats (text and graphics) for the data exist in
the Clipboard, MicroStation chooses the most appropriate
format for displaying the entire graphic.
Alternative method — To paste elements, text,

or linked text from the Clipboard
1. Copy items to the Clipboard from any application.
3. If you want to specify a certain format in which to paste the
information, from the Edit menu, choose Paste Special.
The Paste Special dialog box opens.
4. In the list box, select the format in which you want to
paste the graphic and click Paste.
5. Enter a data point to place the Clipboard data into the design file.
The text is placed using the active text settings as a text node
element with its origin at the position where the data point was
entered. The only formatting retained with the text is line breaks.

To start the application that is the source

of linked text in the design
1. Double-click the text.
To paste a bitmapped graphic in the design

1. Copy the image to the Clipboard from any application.
3. From the Edit menu, choose Paste Special.
4. In the dialog box, select the bitmapped graphic
format and click Paste.
An outline of the image dynamically displays.
5. Enter a data point to place the image in the design.
In 3D design files, pasted bitmaps are easiest to handle if they

are pasted in a Top view. If you place bitmaps in a view that
is not a Top view, the handles that appear when you select the
image work properly but may appear skewed.
The image is saved in the design file as a type 87/88 raster element.
Pasting audio notes

Windows’ Sound Recorder applet can copy audio notes stored
as “.wav” files to the Clipboard. Audio Notes can be pasted
as linked objects in a design file.
To paste an audio note

1. Copy the audio note to the Clipboard.

4. In the dialog box, select the Audio note format and click Paste.
5. Enter a data point to place the audio note in the design (marked
by an icon that looks like a microphone).
To play an audio note

1. Double-click its icon.
Alternative method — To play an audio note

1. From the Edit menu, choose Links.
The Link Manager dialog box opens.
2. In the Link list box, select the audio note’s DDE string.
3. Click the Open Source button.
The source “.wav” file must be available for the audio note to be played.
The reference to the “.wav” file is user attribute data associated with
the microphone bitmap, a type 87/88 raster element.
Pasting animation sequences

Animation sequences can be pasted as linked objects in a design file.
To paste an animation sequence

1. Copy the animation sequence to the Clipboard.
4. In the dialog box, select the Animation sequence
format and click Paste.
5. Enter a data point to place the animation sequence in the design
(marked by an icon that looks like a reel of film).

Sending views to other applications
To play an animation sequence

1. Double-click its icon.
Alternative method — To play an animation

sequence
1. From the Edit menu, choose Links.
The Link Manager dialog box opens.
2. In the Link list box, select the animation’s DDE string.
3. Click the Open Source button.
The source “.avi” file must be available for the animation

sequence to be played.

In Windows, you can use MicroStation to send views to other
applications. You can do this by using OLE2 or DDE. These
technologies allow you to exchange data by linking or embedding.
OLE2 allows document objects from MicroStation to be served to other

applications called containers (applications such as Microsoft Word
or Excel). A MicroStation view object is a picture of a MicroStation
view that can be modified. The primary purpose of the OLE2 document
technology is to provide seamless integration of MicroStation view
objects into container document by embedding or linking.
As you are sending view objects, you must decide if you want
to send them by linking or embedding.
• Link — A linked object is a view object that appears in a container

application but actually lives in its source application. Changes to
the source object are automatically updated in all of the links.
• Embed — An embedded object is a view object that lives
in its container application. Changes to the source object

do not affect the embedded object; you can only edit an

embedded object through its container.
You can only serve views to other applications; you cannot

serve single elements or selection sets.
General Procedure — To Serve a View Object

1. Load the OLE2 Server.
See To load the OLE2 Server on page 5-68.
2. Capture the view object.
See To capture a view object on page 5-68.
3. Embed or link the view object in a container file.
See To embed a view object in a container using OLE2 on page 5-69
or To link a view object to a container using OLE2 on page 5-69.
4. If necessary, edit the view object.
See To edit an embedded view object from the container on page
5-69 or To edit a linked view object from the container on page 5-69.
To load the OLE2 Server

1. In MicroStation’s Key-in window, type MDL LOAD OLESERVE
To capture a view object

1. In MicroStation’s Key-in window, type OLESERVE
VIEWCOPY [view_number]
To capture a MicroStation view object using DDE

1. In the Key-in window, key in CLIPBOARD VIEWCOPY
2. Select the view to be copied.

Editing View Objects in Other Applications
Editing View Objects in Other Applications

How you edit the view object depends on whether you served
it by embedding or linking.
To embed a view object in a container using OLE2

1. In the container, open the document into which you
want to embed the view object.
2. From the container’s Edit menu, choose Paste Special.
3. In the As list box, select MicroStation View Object.
4. Select Paste and then click OK.
To link a view object to a container using OLE2

1. In the container, open the document to which you want
to link the view object.
2. From the container’s Edit menu, choose Paste Special.
3. In the As list box, select MicroStation View Object.
4. Select Paste Link and then click OK.
While only the captured view object displays in the container,
OLE2 copies the entire design file, including attached
reference files, to the Clipboard.
If you select Picture in the As list box, the view object will not be
editable. You will be able only to resize in the container.
To edit an embedded view object from

the container
1. In the container, double-click the view object you want to edit.
MicroStation opens a new file entitled, “Embedded
[filename] MicroStation.” (Note that the original source
design file is not modified.)

Updating view objects
2. Edit the object in MicroStation.

3. From MicroStation’s File menu, choose Exit.
The design file closes, and you are returned to the container
where the updated view object.
To edit a linked view object from the container

1. In the container, double-click the view object you want to edit.
MicroStation opens your original source design file.
2. Edit the object as desired in MicroStation.
3. From MicroStation’s File menu, choose Exit.
The design file closes, and you are returned to the container
where the updated view object displays.
If you return to the container after editing a linked view object

without saving the edits in MicroStation, you can update the
view object in the container by choosing Links from the Edit
menu and clicking the Update Now button.
While only the captured view object is displayed in the

container, OLE2 copies the entire design file, including attached
reference files, to the Clipboard.

Once a link is established, you can update the view in MicroStation,
and it is automatically updated in the container when the appropriate
document is opened. Also, each time a container document that
contains a linked view object is opened, MicroStation opens to update
the view object, closes, and then returns to the container.

To update a previously captured MicroStation

view object
1. Close MicroStation.
The previously stored information updates to reflect
the most current edits.
If (in the Preferences dialog box under the Operation category)
“Immediately Save Design Changes” has been disabled, the
information updates by choosing File menu > Save.
Alternative method — To update a previously

captured MicroStation view object
1. In the Key-in window, key in: OLESERVE UPDATE
The previously stored information updates to reflect
the most current edits.
Notes regarding view objects

The following notes explain processes associated with embedding,
linking, and editing view objects.
• File operations such as Save or AutoSave in the container

automatically close MicroStation. It is recommended
that you disable AutoSave in the container while editing
embedded MicroStation view objects.
• You may not be able to view your view object on the
Clipboard in MicroStation. However, once you open the
container, the view object is available if the Paste Special
item is enabled in the Edit menu.
• Once a link is established you can update the view in
MicroStation, and it may automatically update in the container
when the appropriate document is opened.
Each time a container document that contains a linked view
object is opened, MicroStation opens to update the view
object, closes, and then returns to the container.
• If defined, the configuration variable Embed Reference
Files (MS_OLESERVE_EMBED_REFFILES) determines

OLE Container
whether reference files are embedded along with the active

design file (the view object). By default the configuration
variable is undefined. See To set the Embed Reference
Files configuration variable on page 5-72.
If an embedded view object contains reference file data, the
path information in the Reference Files dialog box indicates
whether the reference file has also been embedded.
Embedded reference files can be active in only one view object at
a time. Attempts to use the same reference file attached twice
to the same embedded design may result in the second and
subsequent attachments referencing the files externally.
To set the Embed Reference Files

configuration variable
2. Select MS_OLESERVE_EMBED_REFFILES.
3. Click Select.
An Alert box opens prompting you to set the configuration variable.
4. Click OK.
5. In the Configuration Variables dialog box, click OK to save
the changes and close the dialog box.
OLE Container
MicroStation allows you to serve view objects to other applications (see
Sending views to other applications on page 5-67); you can also link
or embed objects from other applications into design files.
Linking and embedding objects in MicroStation

A linked object is a document that can be viewed from its container
application, but actually exists in its source application. An embedded
object is a document that actually becomes part of the container
application. When using OLE Container, MicroStation is the container

OLE Container
application. To link or embed an object to a design file, both the source

application and MicroStation must be loaded on the same system.
Use linking when you want to include the same information in

several different design files. When you edit the source file,
MicroStation automatically updates the changes in each design file
containing the linked object. You also have the option of manually
updating your linked objects (see page 5-76) .
Use embedding when the information in the object pertains only

to the design file. Editing an embedded object opens the document
in the source application, but changes made to it are still saved
in the design file in which it is embedded.
To link or embed another application’s document

by pasting the document by its size
1. In the source application, select the part of the document
you want to link, and copy it.
2. In MicroStation, choose Edit > Paste Special.
3. Select the Linked [object type] option in the list box.
or
Select the Embedded [object type] option in the list box.
In this example, “Linked Microsoft Excel Worksheet”

displays. This item changes depending on which source
application you are pasting from.

OLE Container
4. Click Paste.
A second Paste Special dialog box opens.
5. Set Method to By Object’s Size.

6. In the Working units per inch field, type the desired ratio.
7. Enter a data point to define the placement of the document.
8. Enter a data point in the view to accept.

by pasting the document by two corner points
1. Follow steps 1–4 in the preceding procedure.
2. Set Method to By 2 Corner Points.

The pointer changes to crosshairs.
3. Enter a data point to define one corner.
4. Enter a second data point to define the diagonally opposite corner.

by pasting the document by its minimum text size
1. Follow steps 1–4 in the procedure “To link or embed
another application’s document by pasting the document
by its size” (see page 5-73) .

OLE Container
2. Set Method to By Object’s Minimum Text Size.

3. In the Working units per inch field, type the desired ratio.
4. Enter a data point to define the placement of the document.
5. Enter a data point in the view to accept.
MicroStation only supports True Type fonts. If the True Type fonts
you are using in your source applications are not currently used in
MicroStation, you may want to install them. Otherwise, MicroStation
substitutes the active font (Element > Text). Because the source
application defines the text by the font it is using, substituting
another font may give undesirable results.
Editing and updating linked and embedded objects

To edit a linked or embedded object, double-click the object in the
design file. The document opens in the source application.
By default, linked objects are updated automatically if the container

design file is open. For example, if the document is a spreadsheet,
clicking another cell automatically updates the object in the design file.
Edits to embedded objects are always updated automatically.
For linked objects, you can also edit the source document by opening
it directly from the source application, without having to open
MicroStation. You can update the linked object by double-clicking
it the next time you open the container design file.
If you do not want a linked object to update automatically, you can

change its Update status to Manual. That is, the linked object will
only be updated in the design file when you need it.

OLE Container
To change the Update status of a linked object

1. From the Edit menu, choose Object Links.
The Links dialog box opens.
2. Select an item(s) from the list box.

3. At the bottom of the dialog box, set the Update status
to Automatic or Manual.
4. Click Close.
To manually update linked objects

1. From the Edit menu, choose Object Links.
The Links dialog box opens.
2. Select an item(s) from the list box.
3. Click Update Now.
4. Click Close.
The selected linked object(s) is updated in the design file.
Although double-clicking an embedded object opens the document in

the source application, that document is actually just part of the design
file. Note that the name and path of the design file appears in the title
bar of the document. Closing the design file closes the document
(and the source application in which you were editing it).

OLE Container
OLE Container configuration variables

The following are the configuration variables you can define in
MicroStation to customize the display of linked and embedded objects.
Variable New Value Description

MS_OLEC- MicroStation Allows you to
NTR_FONTMAP_<Win- font select another font
dows font> besides the original
font used in the
source application.
Otherwise, if the
source application’s
font is not imported,
the Active font is
used.
MS_OLECNTR_CON- 0 for individual Makes all the text
FIG_UseInterCharac- text characters. in a cell act as a
terSpacing 1 for text strings. single text string.

OLE Container
Variable New Value Description

MS_OLECNTR_CON- 0 for text and Typically, objects
FIG_CreateObjectsAsCells lines. brought into
1 for cells. MicroStation using
OLE are cells. If a
cell is over 128k (the
cell size limit), it is
dropped to text and
lines. This variable
lets you decide if the
objects will always
be cells or not.
MS_OLECNTR_CONFIG_Al- 0 for both Quattro Pro (and
lowFilledBackgroundText variables. possibly other
MS_OLECNTR_CONFIG_Al- applications) uses
lowFullImageFill filled objects as
typical background
color for each cell
and as one large fill
area over the entire
spreadsheet. When
objects are brought
into MicroStation
using OLE, those
filled objects cover
the text you want
visible. These
variables change
them so they are
not filled.
Notes regarding source application limitations

The following sections explain some of the limitations that you may
encounter when linking and embedding from other applications.
Font height and weight

The font that is used in the source application can be easily changed in
MicroStation, but the height and width of the font may not be. These

OLE Container
attributes are determined by the source application. If that application

does not supply a way to change these settings, then the height and
width of the font remains unchanged when linked or embedded in
MicroStation. Microsoft Excel is a good example of this limitation.
Clipboard data
Microsoft Excel only copies a certain amount of complex data to the
Windows clipboard. MicroStation uses this data to recreate the text
and cells. Unfortunately, there is no way in MicroStation to control this
Windows limitation. To find out when you have reached this limitation:
1 . Open the Windows clipboard viewer. If you are using

Windows 95, you may have to install it.
2 . Choose Window > Clipboard.
3 . Choose View > Picture. This option shows you what

information is available for use with OLE. The graphics that
appear represent what can be linked.
This limitation applies to other Windows applications as well.
Page size
Microsoft Excel does not copy horizontal complex data that it thinks is
outside the width of a typical printed sheet of paper. This limitation
is not due to the number of columns, just the physical space. To find
out if this limitation applies to a Microsoft Excel spreadsheet:
1 . In Microsoft Excel, select all of the spreadsheet’s cells.
2 . Hold down the áShiftñ key and choose Edit > Copy Picture. This
option is only available when holding down the áShiftñ key.
3 . Select “As shown on screen” and “Picture,” then click OK. If

the message, “The picture is too large and will be truncated”
appears, then you have exceeded the page limit.
To correct this problem, reduce the size of all of the cells

using the Format menu. (Use a similar process for other
spreadsheet applications.)

Sending key-ins to MicroStation through a DDE link
Sending key-ins to MicroStation through a DDE link

You can send key-ins to MicroStation through a DDE link. For
example, you can create a macro in a spreadsheet that starts a DDE
“conversation” with, and send key-ins to, MicroStation.
MicroStation understands these types of DDE requests:
• INITIATE — establish a DDE link with MicroStation.

• EXECUTE — pass key-in(s) to MicroStation.
• TERMINATE — end DDE conversation with MicroStation.
Applications that can make these DDE requests include Excel, Lotus
1-2-3, Object Vision, Visual Basic, Word Basic, and others.
To send a key-in to MicroStation via DDE

link from an application
1. Send the INITIATE request to establish the DDE
link with MicroStation.
2. Use the EXECUTE request to send the key-ins to MicroStation.
3. Send the TERMINATE request to end the conversation
with MicroStation.
In each of these steps, you use the syntax of the application that is
sending key-ins to MicroStation to make the DDE requests.
Sample DDE “conversation”

The following Microsoft Excel macro rotates the contents of
MicroStation’s View 1 in 5 increments about the horizontal axis:
In this macro, chan is any Excel variable name. It is needed to refer to

this particular conversation in subsequent DDE requests. The rest
of the contents of the macro are explained in this table:

Importing Text
chan =INITIATE("Ustn","Keyin") Opens the conversation

with MicroStation. The
constants Ustn and Keyin
are mandatory.
=EXECUTE(chan,"rv=5") Passes the key-in RV=5
to MicroStation.
=FOR("Count",1,40) Starts a loop for 40 times.
=EXECUTE(chan,"selview 1") Uses the key-in SELVIEW

1 to simulate the entry of a
data point in View 1.
=NEXT() Marks the end of the loop.
=TERMINATE(chan) Terminates the DDE

conversation with
MicroStation.
=RETURN() Marks the end of the

Excel macro.
Importing Text
You can create a text file using a word processing, text editing,
or other type of application and import the contents of the
text file into a MicroStation design.
To place the contents of a text file in the design

1. (Optional) — To set the number of space characters that
will be substituted for each Tab character in the file, key
in ACTIVE TAB [spaces] or TB=[spaces].

Using Redline Files
2. From the File menu’s Import submenu, choose Text….

The Include Text File dialog box opens.
Include Text
File dialog
box
3. Select the file and click OK.

The text contained in the file dynamically displays.
4. Enter a data point to position the text.
If the file is larger than 128 lines or 2048 characters, the text does
not display dynamically and is placed as a graphic group. The
data point positions the upper left corner of the text block.
Otherwise, the text is placed as a text node and the data
point positions the text node origin.
The file can include MicroStation key-in strings to set text attributes
(such as the font, text size, line spacing, and line length). Each
key-in string must follow a period (“.”) that begins a line. One
key-in string is allowed per line. All text following a key-in string is
placed with the specified attribute. Other text placement controls
can be included: INDENT # indents by the specified number of
columns. NEWGG begins a new graphic group.
Using Redline Files

MicroStation enables you to work with redline files created
with MicroStation PowerScope.

Redline tool box
The redline file is a special type of reference file. If a redline

file is attached to the active design file, it is automatically
detached when the design file is closed.
Redline tool box

The tools in the Redline tool box are used to attach and
manually detach the redline file.
To Select in the Redline

tool box
Attach a redline file
Attach Redline File

(see page 5-83)
Detach a redline file
Detach Redline File

(see page 5-84)
Key-in: DIALOG TOOLBOX REDLINE OFF | ON | TOGGLE
Attach Redline File

Used to attach a redline file to the active design file.
To attach a redline file to the active design file

1. Copy the redline file to the same location as the active design file.
2. Create and define the configuration variable (see page 3-7)
RDL_DIR to point to the location of the newly copied redline file.
3. Select the Attach Redline File tool.

Detach Redline File
Key-in: REDFILE ON
Detach Redline File

Used to detach a redline file from the active design file.
To manually detach the redline file

1. Select the Detach Redline File tool.
Key-in: REDFILE OFF

Building Custom Projects
This chapter covers projects, the component of MicroStation’s
workspaces that comprises the data files used for a particular
discipline or undertaking. A project manager can create projects
for consistency among a number of users, and a single user can
create projects to quickly customize MicroStation’s environment
for different projects and customers.
There are four steps to building and preserving a custom project:
1 . Designing a Module (see page 6-1) includes establishing file

naming conventions and a directory structure for the data.
2 . Assembling Module Data Files (see page 6-4) .
3 . Modifying the Project Configuration File (see page 6-96) .
4 . Archiving: Bundling Module Data Files (see page 6-97)

associated with a specific design file.
Designing a Module
A module is a collection of data files that are organized
to take advantage of MicroStation’s workspace feature.
Module files can include:
• Design Files (as samples or for use as reference files).
• Seed Design Files (see page 6-4) and Seed Sheet Files.
• Cell Libraries (see page 6-6) , including those with
Dimension-driven Cells (see page 6-8) .
• Level Structure Files (see page 6-55) .
• Color Tables (see page 6-61) .
• Line Style Libraries (see page 6-65) .
• Settings Files (see page 6-84) .

Sample modules delivered with MicroStation
• Material tool box and Material Assignment Table Files

(see Surface material definitions).
• Tag set libraries.
• Tag Report Template Files (see Reporting on Tags).
• Glossary files.
• Font Libraries.
• Function Key Menuspage 4-27.
• Menu Cell Libraries that contain the specifications for
Digitizing Tablet Menuspage 4-29.
• Tutorial Cell Libraries that contain the specifications
for Tutorialspage 4-41.
Of course, a module need not contain all of these file types.
A workspace’s project component can specify or “point to” data

files in many modules. However, for the sake of this introduction
to designing modules, it will be assumed that each module is
associated with a particular project.
The sample modules delivered with MicroStation are examples

of module design. (If you already deal with many data files, you
may already have “modules” on your system or network.) The
Architecture module is shown as an example of how a module
can be organized in Sample modules delivered with MicroStation
(see page 6-2) . The advantages of this structure are discussed
in Module design goals (see page 6-3) .
Sample modules delivered with MicroStation

The sample modules are delivered by default in Bentley’s
“Workspace\projects\examples” directory.
The “arch” module is one of the delivered samples:
The “arch” module

arch
cell

Module design goals
The “arch” module

“arch.cel”
“archpat.cel”
(and so on)
data
“aiaarch.lvl”
“aiacivil.lvl”
“arch.gls”
(and so on)
dgn
“border_d.dgn”
“igi_flrp.dgn”
“lad_dia.dgn”
(and so on)
out
(initially empty)
seed
“archseed.dgn”
“sdarch.sht”
“sdarch3d.dgn”
(and so on)
symb
“archlsty.rsc”
(and so on)
Module design goals

These are some of the design goals you should have in mind
when you design your own modules.

Assembling Module Data Files
Creation, maintenance, and removal

The modules should be kept in parallel directory structures
that make it easy to create new modules, to add or delete files
in the modules, and to remove entire modules.
File duplication
If data files are shared by two or more projects, to avoid creating
an administrative nightmare of duplicate files, do not put a copy
of each shared data file in each module that needs it. Since the
data files are specified by configuration variables in the project
configuration file, different projects can easily specify any file
in any module. In other words, no one-to-one correspondence
between project and module is required.
The user configuration file and user preference file should be kept
on local systems, not on a network. In no case should two users try
to simultaneously write to the same user configuration file or user
preference file. MicroStation reads these files for some operations and
does not expect to find the file open (and locked) by another user.
Assembling Module Data Files

The sample workspace modules contain many examples of data files.
You may find these appropriate for inclusion in your workspace
module. If so, assembling module data files is simply a matter
of copying the files from the sample workspace modules into the
directory structure you have designed for your module.
Should you wish to create module data files, MicroStation’s settings
boxes and dialog boxes make it fairly easy. Each of the following
sections cover how to create a different type of module data file.
Seed Design Files

Seed design files and seed sheet files are simply design files that
are copied to create design files and sheet files.

Seed Design Files
General Procedure — To create a seed file

1. Open any design file. It is recommended that you open a copy
of an existing seed file. The following “generic” seed files are
installed in Bentley’s “Workspace\system\seed” directory.
Intended use File

3D design/model (English units) “seed3d.dgn”
3D design/model (metric units) “3dm.dgn”
2D design (English units) “seed2d.dgn”
2D design (metric units) “2dm.dgn”
A-size drawing sheet, landscape “seedah.sht”
orientation
A-size drawing sheet, portrait “seedav.sht”
orientation
B-size drawing sheet “seedb.sht”
C-size drawing sheet “seedc.sht”
D-size drawing sheet “seedd.sht”
E-size drawing sheet “seede.sht”
F-size drawing sheet “seedf.sht”
2. From the File menu, choose Save As.

The Save Design As dialog box opens.
3. In the Files field, key in the name for the new seed file.
5. Place elements that you want to include in all designs that
will be created using the new seed file. Most seed design
files do not contain any graphical elements. Seed sheet
files typically contain a drawing border.
6. Adjust settings to be appropriate for starting a design. See
Preparing to Drawin the User’s Guide.
7. Arrange the view configuration to be appropriate for starting a
drawing. See Arranging View Windowin the User’s Guide.

Cell Libraries
8. From the File menu, choose Save Settings to save the settings
and view configuration in the design file.
9. Close the design file.
Cell Libraries
Cell libraries are perhaps the most common type of file assembled
as module data. They contain cells, which are small drawings —
usually of frequently-used or complex symbols.
To create an HTML Web page that displays the contents of a cell library,
use the HTML Author dialog box (Utilities menu > HTML Author).
To build a cell library

1. Create the cell library and attach it to the active design file.
or
If the cell library already exists, attach it to the active design file.
See To attach a previously existing cell libraryin the Using
2. Create the desired cells in the library.
For any cell that does not exist in another library, create it “from
scratch” by following the steps in “To designate a cell as an active
cell”in the Using Cells chapter of the User’s Guide.
For any cell that already exists in another library, follow
the same steps but instead of drawing the cell, merely place
the cell using a tool in the Cells tool box. (For information
about activating cells from unattached libraries, see “Using
multiple cell libraries” on page 6-6.)
Using multiple cell libraries

If you key in ACTIVE CELL <CELLNAME> or AC=<CELLNAME>, if
the cell is not a shared cell in the design or in the attached cell library,
or if there is no attached cell library, MicroStation searches for the cell
in the cell library list specified by the Cell Library List configuration
variable (MS_CELLLIST). Cell libraries are searched in their order in
the list. If wildcard characters are used, cell libraries are searched in
alphabetical order. For example, if MS_CELLLIST expands to:

Using multiple cell libraries
Bentley\Workspace\projects\proj1\cell\master.cel;Bent-
ley\Workspace\system\cell\p*.cel
and the files “projcel.cel,” “pipe2.cel,” “house.cel,” and “peter.cel” are

in the “Bentley\Workspace\system\cell” directory, MicroStation
searches for a cell as follows:
1 . In the attached cell library.
2 . In “Bentley\Workspace\projects\proj1\cell\master.cel”.
3 . In “Bentley\Workspace\system\cell\peter.cel”.
4 . In “Bentley\Workspace\system\cell\pipe2.cel”.
5 . In “Bentley\Workspace\system\cell\projcel.cel”.
To make it easier to attach different cell libraries, an item for

each cell library in the cell library list is appended to the File
menu in the Cell Library dialog box.
Default
cell library
list for the
sample “arch”
workspace.
All files in the specified directory with the “.cel” extension are listed
in the File menu in the Cell Library dialog box. Any cell in any
listed cell library can be placed by keying in AC=<CELL_NAME>,
regardless of whether its cell library is attached.
To attach a cell library that is in the cell library list

1. From the File menu in the Cell Library dialog box,
choose the cell library.
Cell libraries in the cell library list must have a cell library
index file. The first time a cell library is attached, MicroStation
automatically generates the cell library index file.

Dimension-driven Cells
3D cell libraries cannot be used if the active design file is 2D.
Nested cells are always expanded from the same cell

library as their parent.
Dimension-driven Cells
A dimension-driven cell is based on such a model and serves as a
template for a family of cells that can be derived — solved for a
specified set of dimension values. Constraints and constructions
represent a dimension-driven cell’s underlying structure. A derived
cell is a cell in a design that is derived from a dimension-driven cell.
Dimension-driven design tools are used to specify constraints and
constructions that determine the size, extent, or shape of associated
elements in the model. All dimension-driven design tools are in
the DD Design tool frame (see page 6-15) .
The dimensions and constants on which a dimension-driven

cell are based can be modified with the Dimension-Driven
Design dialog box (see page 6-54) .
The Dimension-Driven Design dialog box is also used to

place derived cells. See Dimension-driven Cells in the Using
Concepts and terminology

This section has definitions of basic terminology and other introductory
information about dimension-driven cell creation.
Important terminology
The following terms are important for understanding
dimension-driven cell creation:
Constraint — a piece of information that limits or controls a

construction. See also Constraints (see page 6-9) .

Construction — an element (point, infinite line, circle, ellipse,

or B-spline curve’s control polygon) that lets constraints locate,
delimit or arrange other elements. For example, a construction
line can be the center line of a symmetric design.
Well-constrained — a set of constructions that is completely defined

by constraints or is constant and has no redundant constraints.
There is generally more than one feasible solution for a set of
well-constrained constructions, but the choice is usually clear.
Under-constrained — a set of constructions that is not

completely defined by constraints and is not constant. An
under-constrained construction has many possible “solutions”
and is unacceptably ambiguous.
Redundant — A constraint that is applied to a set of constructions

that are already well-constrained. A redundant constraint
may or may not be inconsistent with other constraints, but, in
either case, it adds no useful information.
Degrees of freedom — Number that sums up a dimension-driven

cell’s ambiguity.
Solve — To construct the design from a given set of constraints

and show what remains to be defined.
Constructions are elements with the class construction

and special symbology (see Diagnosing an ambiguous
dimension-driven cell on page 6-11).
Constraints
Constraints say what characteristics a dimension-driven cell
must have, but not necessarily how to arrive at a design with
those characteristics. How to compute geometry in the light
of constraints is the task of “solving.”
Most constraint relationships apply to the design’s essential

layout or general structure. The design’s details are located and
shaped by its structure. For example, if a dimension-driven
cell is generally symmetrical, it has constraints that relate
elements to a center line in some way.

Constraints are applied using the tools in the Constraint tool box.
The following types of constraints can be created:
• Location — A constraint that fixes the location of a

point in the design plane.
• Geometric — A constraint that controls the position or
orientation of two or more elements relative to each other.
• Dimensional — A constraint that is a controlled by a dimension.
• Algebraic — An equation that expresses a relationship
among variables.
When a constraint is added, modified, or deleted, the model is resolved

— an attempt is made to reconstruct the design so that the new or
modified constraint, as well as all existing constraints, are satisfied.
• If a solution is found, the affected elements are updated and

redisplayed. The solution may affect elements that are not
obviously or locally related to the new constraint.
• If no solution is possible, the message “Not Solved” and
graphical cues as to where the trouble is are displayed. The
design’s geometry is not updated, but the constraint is accepted
anyway. If MicroStation reports “Not Solved” even though the
new constraint is not redundant and you are sure that a solution
is in fact possible, it may help to re-arrange the geometry of the
model to look more like the solution you want and then re-solve.
Adding a new constraint removes ambiguity from the design.

(Deleting a constraint has the opposite effect.)
A constraint can apply only to a construction. An element is converted

to the equivalent construction when a constraint is applied to it.
Most location and geometric constraints are assigned the class

Construction. You can define the level and class of dimensions, location
constraints, and equations. In the future, you will be able to specify the
level, symbology, and class of all constraints and constructions.

Diagnosing an ambiguous dimension-driven cell

The symbology of constrained elements and of the constraint
and dimension elements themselves alert you to ambiguities
and inconsistencies in the design.
• If a construction or variable is completely defined by

constraints or is constant, it is well-constrained and
is displayed in solid white.
• If a construction or variable is not completely defined
by constraints, it is under-constrained and is displayed
dashed in yellow.
• If a constraint is applied to a set of construction that are already
well-constrained, it is redundant and is displayed dashed in red.
Valid constraints are displayed as follows:
Constraint Displayed In
Dimensions solid white
Other geometric constraints solid blue
Equations white
The remaining ambiguity in a design is summed up by a
number called “degrees of freedom.” Each new construction
adds degrees of freedom as follows:
Construction Degrees of
Freedom
Added
Point 2
Line up to 4
Circle up to 3
Ellipse up to 5
Each valid constraint removes one or more degrees of freedom.
A well-constrained design has zero degrees of freedom and no redundant

constraints. All constructions are well-constrained (displayed in white).
If the number of degrees of freedom is not zero, then parts of the

design are under-constrained (displayed in yellow).

Equation syntax
When a constraint is added, the remaining degrees of freedom

are displayed, followed by the message “Over-constrained” if
there are any redundant constraints.
Equation syntax
An equation consists of an algebraic expression (or just a variable),
optionally followed by an equals “=” sign and another algebraic
expression. For example, “a + b = c^2” is an equation relating a, b,
and c. If just one expression is given, “= 0” is assumed. For example,
the equations “a + b = 2” and “a + b - 2” mean the same thing.
Constant expressions are valid in equations. A constant expression

is an algebraic expression involving numbers, operators, built-in
functions and built-in constants (like pi).
Algebraic expression
An algebraic expression can contain variable identifiers, numbers,
arithmetic operators, and built-in functions and constants,
according to the usual rules of algebra.
Formally, the grammar of an algebraic expression is as follows:
Clause Grammar
exp2: exp1 [ [op2] exp2 ]*
exp1: [op1]* exp0
exp0: ‘(’ exp ‘)’ | variable | number | const
op2: binary arithmetic operator
op1: unary operator or built-in function
const: numerical constant reserved word
number: integer, floating point, exponential,
or mu:su:pu notation
variable: user-defined variable identifier
[ …] denotes an optional clause

Equation syntax
* means zero or more clauses
| separates alternatives quotes
‘…’ denote a literal character.)
Fractional clauses are valid in algebraic expressions. A fractional

clause has the following grammar:
‘#’ integer integer ‘/’ integer ‘#’ (example: #2 1/2#)
In number clauses, distances and coordinates can be expressed in

working units (MU:SU:PU), decimal, or fractional notation.
The multiplication operator * is not assumed. Omitting an

operator is a grammatical error.
White space and comments

White space and comments can appear anywhere in an
expression and are ignored.
A comment is a sequence of characters enclosed in brackets or

braces, as follows: ‘[’ ...‘]’ | ‘{’ ... ‘}’ | ‘/*’ ... ‘*/’
Arithmetic operators
The following arithmetic operators are available:
Operator Operation Performed

- arithmetic negation
cos cosine
sin sine
tan tangent
acos arccosine
asin arcsine
atan arctangent

Equation syntax
Operator Operation Performed

sqrt square root
+ addition
- subtraction
* multiplication
/ division (floating point)
% modulo
^ exponent (e.g., a ^ 2 squares the value of a)
= equal to
Built-in numerical constants
The following built-in numerical constant is available:
Constant Means
pi π
Numbers
A number can be expressed in integer, floating point or exponential

notation, followed by an optional units keyword, or in working units
notation (mu:su:pu). Units keywords are as follows:
Keyword Units Denoted

deg degrees (for angles)
Variable names
A variable name can have up to 32 characters, beginning with a letter
or underscore, followed by letters, numbers or underscores, with no
embedded blanks. Variable names are case-sensitive.

DD Design tool frame
A variable name cannot be the same as a built-in function or

constant, but may contain a reserved word as part of its name. For
example, if “sin” is a built-in function, then “sin” is not a valid
variable name, but “sin_of_x” is valid. Reserved names are not case
sensitive, so “Sin” is not a valid variable name.
A variable’s name must be unique within the cell or

sub-design in which it is used.
DD Design tool frame

Tools for creating and modifying dimension-driven profiles and
cells are accessed from the DD Design tool frame.
To Use tools in the

Sketch a profile,
or
Convert an element to a profile.
Profile tool box (see
page 6-16)
Convert dimensions to constraints,
or
Assign equations to variables,
or Parameter
Assign variables to dimensional Constraints tool box
constraints. (see page 6-23)
Construct an arc, line string, or

shape that is attached to one or
more constructions.
Attach Element tool
box (see page 6-27)

Profile tool box
To Use tools in the

Create geometric constraints.
Geometric Constraints
tool box (see page 6-32)
Evaluate, modify, and re-solve constraints
for dimension-driven profiles.
Evaluate Constraints
tool box (see page 6-42)
Break or trim constrained geometry,
or
Add fillets and chamfers to constrained
geometry, Modify Constraint tool
or box (see page 6-47)
Modify dimension or variable values.
Key-in: DIALOG TOOLBOX DDDTOOLS OFF | ON | TOGGLE
Profile tool box

The tools in the Profile tool box ar eused to sketch a profile
and convert an element to a profile.

Sketch Profile
To Select in the Profile

tool box
Sketch a geometrically-constrained
profile.
Sketch Profile (see

page 6-17)
Convert a line string shape or complex
shape to a geometrically-constrained
profile.
Convert Element to
Profile (see page 6-22)
Key-in: DIALOG TOOLBOX DDDDRAW
Sketch Profile
Used to sketch a dimension driven profile. When using this tool, geometric
constraints are automatically applied to the profile as it is being created.
Constrained profiles will have a fixed point (a point relative
to which dimensional modifications are performed) when the
Location constraint is turned on in the Sketch Profile tool settings
window. A fixed point can be relocated on the profile.
As you create a sketch with the Sketch Profile tool, geometric
constraints are automatically applied and dimensional constraints
are applied to rounded or chamfered connections.
Tool Effect
Setting
Segment Sets the type of segment being sketched: Line,
Arc by Center, Arc by Edge, Curve.

Sketch Profile
Tool Effect
Setting
Vertex Sets the type of connection at a vertex.
Sharp—Simple intersection point.
Rounded—Creates an arc.
Chamfered—Creates a chamfer.
Tangent—Creates a tangent point between a line

and an arc or between two arcs.
Geomet- If on (the default), geometric constraints are
ric Con- added as the profile is sketched, according to
straints the Rules for applying constraints.
Type (Segment set to Curve only) Sets the method by which
the curve is sketched: Define Pole or Through Points.
Order (Segment set to Curve and Type set to Define
Poles only) Sets the Order of the equation that
defines the curve. Default Order is 4.
Radius (Vertex set to Rounded or Chamfered only) Sets the
radius of the circle used to construct the connection.
Set Text If On, automatically sets height and width of
Size Au- dimension text and constraint symbols.
tomati-
cally
Set Tol- If On, automatically sets Distance and
erances Angle tolerances. If Off, Distance and Angle
Automat- tolerances are set by user.
ically
Distance Tolerance—Sets the distance within
which points are located to unify.
Angle Tolerance—Sets the angle within

which elements are located for parallel and
perpendicular constraints. Also snaps lines
parallel to 0 , 45 , or 90 .

Sketch Profile
Tool Effect
Setting
Con- The following constraints are automatically
straints applied to the profile, when on.
Unify—Constrains endpoints of two elements, or
the endpoints of a single element, to be united
into a single common point.
Dimension—Converts a dimension to a constraint.
Concentric—Constrains two elliptical/circular

arcs to be concentric.
Parallel—Constrains two lines (or the primary axes

of two ellipses) to the same rotation angle.
Perpendicular—Constrains two lines (or the

primary axes of two ellipses) to be at a right
angle (90 ) to one another.
Fix Angles—Fixes the orientation of a line (or the

primary axis of an ellipse) to 0 , 45 , or 90 ,
when it is within the Angle Tolerance.
Point On—Constrains a point (or the center of a

circle or an ellipse) to lie on a construction.
Tangent—Constrains two constructions to be tangent.
Location—Fixes the location of a point in the design.

Sketch Profile
Tool Effect
Setting
Confirm Confirm whether or not to add the constraint
to the profile, when on.
Constraints are applied when certain
conditions are present:
• A line segment is nearly horizontal (0 ) ,
vertical (90 ), or 45 , and the first linear
segment has a fixed angle constraint.
• The first three vertices of the profile define the
plane of the sketch. Profiles must be planar.
• For a rounded vertex, a circle with a radial

constraint is constructed and attached to
the vertex, and the circle’s radius is set
in the Radius tool setting.
• Dimensional constraints are not applied to
items other than fillets or chamfers.
As each additional segment is drawn, it is checked

for information relative to previously-placed
segments in the following order:
1 . Is it colinear with any existing segment?
If not, then:
2 . Is it parallel to the first segment? If not, then:
3 . Is it perpendicular to the first segment?
If any of these conditions are met, the

constraint is applied.
To relocate a constrained profile’s fixed point

1. From the Settings menu, choose View Attributes.
The View Attributes dialog box opens.
2. Turn on Constructions.

Sketch Profile
3. Select the Delete Element tool from the Main tool frame
and delete the existing fixed location constraint.
4. (Optional) — Turn off Constructions.
5. Select the Fix Point at Location tool (see page 6-41)

from the Geometric Constraints tool box.
6. Identify the point on the profile that is to be the new

fixed point constraint.
7. Enter a data point to accept the fixed point constraint.
Rounds and chamfers can be omitted from the sketch

and applied to the solid.
Rounds and chamfers in the profile can not be deleted.
To sketch a parametric profile

1. Select the Sketch Profile tool.
2. In the Tool Settings window:
From the Segment option menu, choose the segment type.
From the Vertex option menu, choose the connection type.
Turn on Geometric Constraints.

Convert Element to Profile
3. Enter a data point to define the first point.

4. Continue entering data points to define the profile.
Key-in: SKETCH
Convert Element to Profile

Used to convert a line string, shape, complex chain or complex shape to a
geometrically-constrained profile. This tool also works with selection sets.
This tool allows users to create dimension-driven profiles from
existing elements in the design. Users can select the desired
constraint types to apply to the profile, as well as allow MicroStation
to confirm each constraint before it is applied.
Controls in this Tool Settings window are analogous to those
in the Sketch Profile tool (see page 6-17) .
To convert an element to a
geometrically-constrained profile
1. Select the Convert Element to Profile tool.
2. Identify the element or selection set.
3. In the Tool Settings window:
Enter text height and width or accept automatic
size settings (default).
Enter Distance and Angle Tolerances or accept automatic
tolerance settings (default).
4. Click on the Settings button.
The Convert Element to Profile dialog box expands to
display a constraints list.
5. Turn on the constraints to be applied.

Parameter Constraints tool box
6. Turn on confirmations, where required.

7. Enter a data point to initiate the conversion.
The Convert Element to Profile tool also works with a selection set.
In MicroStation, construction elements do not need to be

displayed in the view when converting an element to a
geometrically-constrained profile.
Key-in: CONVERT PROFILE
Parameter Constraints tool box

The tools in the Parameter Constraints tool box are used to apply
dimensional constraints to constructions.
To Select in the
Parameter
Constraints tool box
Convert an associative dimension
into a constraint.
Convert Dimension
to Constraint (see
page 6-24)

Convert Dimension to Constraint
To Select in the
Parameter
Assign an equation to a model.
Assign Equation (see

page 6-25)
Assign a constant or variable to a
dimensional constraint.
Assign Variable
to Dimensional
Constraint (see
page 6-26)
Key-in: DIALOG TOOLBOX DDDPARM OFF | ON | TOGGLE
Convert Dimension to Constraint

The Convert Dimension to Constraint tool is used to convert a dimension
into a dimensional constraint. This tool works only on dimensions that
have not been previously constrained with the Dimension Element tool.
When MicroStation is running, it is possible to convert dimensions
that are not associative. Since a non-associative dimension is not
associated to any element, an attempt is made to link the dimension
to an element based on the possible type of dimensional constraint
the dimension could become, the element type(s) it could apply to,
and the element the dimension touches or is aligned with.
Possible problems when converting a non-associative
dimension are as follows:
• If no suitable element can be found, the message “Targets
not found” displays in the status bar.
• A constraint is created, but it is incorrect or unsatisfactory.
If you cannot satisfactorily convert a non-associative dimension,

delete it and replace it with an associative dimension
to specify exactly the desired constraint.

Assign Equation
To convert a dimension to a dimensional

constraint
1. Select the Convert Dimension to Constraint tool.
2. Identify the dimension and accept.
The Choose Parameter Name dialog box opens.
Type a name for the dimensional constraint in the
Variable field and click OK.
The dimension updates with the variable name and
dimension value.
Key-in: CONSTRAIN DIMENSION
You cannot convert the angle of a line from the X or Y axis, ordinate
dimensions, or the size or location of an arc.
Assign Equation
Used to assign an algebraic constraint — an equation that expresses
a constraint relationship between variables, numerical constants
and built-in functions and constants — to a model.
An equation is stored in a text element and is created using the
Place Text tool and can be edited using the Edit Text tool.
Equation syntax (see page 6-12) follows the rules of algebra. Built-in
functions and pre-defined constants can be used.
To assign an equation to a model

1. Select the Assign Equation tool.
2. Identify the text element that contains the equation.

Assign Variable to Dimensional Constraint
3. Identify one of the equation’s variables or any element in the

model to which the equation is being assigned.
4. An attempt is made to solve and one degree of freedom is removed.
Key-in: CONSTRAIN EQUATION
Assign Variable to Dimensional Constraint

Used to assign a constant or variable to a dimensional constraint. The
constant or variable then represents the dimension’s value in equations.
A constant or variable is created using the Place Text tool and can be
edited using the Edit Text tool. A constant or variable is identified by
name. See Variable names on page 6-14 for naming rules.
To assign a constant or variable to a

dimensional constraint
1. Select the Assign Variable to Dimensional Constraint tool.
2. Identify the text element that contains the constant or variable.
3. Identify the dimensional constraint.
If a variable is assigned, the dimensional constraint’s value
becomes an unknown and one degree of freedom is added.
Key-in: CONSTRAIN VARIABLE
To make a variable constant, use the Edit Text tool to assign

the variable a constant value.

Attach Element tool box
Attach Element tool box

The tools in the Attach Element tool box are used to construct an arc,
line string, or shape that is attached to one or more constructions. Only
the elements size, shape, or location are modified when solving.
To Select in the Attach

Element tool box
Construct an attached line sting or shape.
Construct Attached
Line String or Shape
(see page 6-28)
Construct an attached arc.
Construct Attached
Arc (see page 6-29)
Construct an attached ellipse or circle.
Construct Attached
Ellipse or Circle (see
page 6-29)
Attach an element’s location to a
construction or constraint.
Attach Element to
Point (see page 6-30)

Construct Attached Line String or Shape
To Select in the Attach

Element tool box
Attach an element’s location and
rotation to a constraint.
Align Element with

Point and Line (see
page 6-30)
Cause an element to track a point,
ellipse, or constraint.
Attach Pen Element to

Point (see page 6-31)
Key-in: DIALOG TOOLBOX DDDATTACH OFF | ON | TOGGLE
Construct Attached Line String or Shape

Used to create a line string or shape with its vertices attached
to construction points, circles, or constraints.
To construct an attached line string or shape

1. Select the Construct Attached Line String or Shape tool.
2. Distinguish an existing element to define the first vertex by
entering a data point near the element.
3. Continue identifying elements to define other vertices.

Construct Attached Arc
4. To create an attached shape, enter the last data point

at the starting point.
5. Reset to end the line string or shape.
Key-in: ATTACH LSTRING
Construct Attached Arc

Used to construct an arc that is attached to the identified construction
circle or ellipse. The arc is defined in the counter-clockwise
direction from its beginning to its endpoint.
To construct an attached arc

1. Select the Construct Attached Arc tool.
2. Identify the underlying construction circle or ellipse.
3. Identify an element to define the arc’s beginning, from
which the arc extends counter-clockwise.
4. Identify an element to define the arc’s endpoint.
Key-in: ATTACH ARC
Construct Attached Ellipse or Circle

Used to create and attach a circle to a construction circle
(or an ellipse to a construction ellipse).
To construct an attached ellipse or circle

1. In the Attach Element tool box, select the Construct
Attached Ellipse or Circle tool.

Attach Element to Point
2. Identify the target construction.

3. Accept the attachment.
Key-in: ATTACH CIRCLE
Attach Element to Point

Attaches an element’s (text, cell, line string, or shape) location to a
constraint or construction point. The element then moves whenever the
construction or constraint is moved. The element’s rotation is not changed.
To attach the location of an element to a

construction or constraint
1. Select the Attach Element to Point tool.
2. Identify the element.
3. Identify a construction or constraint to which to attach
the element’s location.
The element is attached to the construction or constraint and
moved to the construction or constraint location.
Key-in: ATTACH LOCATION
Align Element with Point and Line

Attaches an element’s (text, cell, line string, or shape) location
and orientation to a constraint. The element then is moved and
rotated whenever the constraint is moved or rotated.

Attach Pen Element to Point
To attach the location and rotation of an

element to a constraint
1. Select the Align Element with Point and Line tool.
2. Identify the element.
3. Identify the constraint.
The element is attached to the constraint, moved to the
constraint’s location, and rotated to the constraint’s orientation.
Key-in: ATTACH TRANSFORM
Attach Pen Element to Point

Used to cause an element (of any type) to track a point,
ellipse, or constraint, leaving a “trail” behind it.
Whenever the model is re-solved, the “pen element” is moved to the
target point’s location without first being erased from its old location.
A history of images accumulates in the view. A pen attachment is
useful for “range of motion” and interference studies.
To attach a pen element to a point, ellipse,

or constraint
1. In the Attach Element tool box, select the Attach Pen Element tool.
2. Identify the element that is to become the “pen.”
3. Identify the element to which to attach the pen.

Geometric Constraints tool box
To erase a trail of “pen ink” images

1. Update the view.
Key-in: ATTACH PEN
Geometric Constraints tool box

The tools in the Geometric Constraints tool box are used
to create geometric constraints.
To Select in the
Geometric
Constrain geometry to be tangent,
perpendicular, parallel, or fix angle
to horizontal or vertical.
Constrain Elements
(see page 6-33)
Make a variable a constant or
make a construction invariant (not
recalculated when solving).
Make Construction or
Parameter Invariant
(see page 6-38)
Constrain a point (or the center of a circle
or an ellipse) to lie on a construction.
Constrain Point On
Construction (see
page 6-38)

Constrain Elements
To Select in the
Geometric
Constrain a point to the intersection
of two constructions.
Constrain Point at
Intersection (see
page 6-39)
Constrain two points to be coincident,
two circles to the same center, or a
point to the center of a circle.
Constrain Two Points
to be Coincident (see
page 6-40)
Fix the location of a point in the design.
Fix Point at Location

(see page 6-41)
Equate the endpoints of constructions.
Equate Parameters
or Constructions (see
page 6-41)
Key-in: DIALOG TOOLBOX DDDCONSTRAINT OFF

| ON | TOGGLE
Constrain Elements
Used to apply tangent, perpendicular, parallel, or fix
angle constraints to profile geometry.

Constrain Elements
Tool Effect
Setting
Method Sets the method by which to constrain
profile geometry.
Smart Constrain Elements—Constrains constructions
tangent, perpendicular, or parallel, or by fixing
the angle, depending upon the identified
element(s) and the number of data points. This
Method is recommended unless you need to
override or force constraints.
Constrain Two Constructions to be

Tangent—Constrains two constructions (two
circles, two ellipses, a circle or ellipse and a
line) to be tangent at as many points as their
geometry makes possible.
Constrain Two Lines to be Perpendicular—Constrains

two lines (or the primary axes of two ellipses) to
be at a right angle (90 ) to one another.
Constrain Two Lines to be Parallel —Constrains

two lines (or the primary axes of two ellipses)
to the same rotation angle.
Fix Angle of Line or Ellipse—Constrains a line’s

orientation or an ellipse’s rotation angle.

Constrain Elements
Tool Effect
Setting
Fix Angle (Method set to Smart Constrain Elements only)
Snap Tol- Sets the tolerance for constraining a line or the
erance primary axes of an ellipse (that is on an angle)
to the closest view axis (x- or y-).
Used in conjunction with the Smart Constrain
Elements method, this setting forces individually
selected elements to be constrained to the
view x- or y-axis if the current position of the
element is within the tolerance value from a
vertical or horizontal position.
For example, if Fix Angle Snap Tolerance is 10 and
a single line drawn at 45 is identified, the line is
fixed at 45 . If the line was placed at a 5 slope off
the view x-axis, the line is forced to be horizontal.
This setting also forces multiple elements to be
constrained parallel, perpendicular, or tangent
with one another along the view x- and y- axes if
the current position of the elements are within the
tolerance value from a vertical or horizontal position.
Angle (Method set to Fix Angle of Line or Ellipse only)
Lock Constrains a line or the primary axes of an
ellipse by the following options.
None—Geometry is constrained at the
angle it was created.
Horizontal—Geometry is constrained to
the view x-axis.
Vertical—Geometry is constrained to the view y-axis.

Settings Toggles the display of the Convert to Constructions
and Join Ends at Junctions check boxes.

Constrain Elements
Tool Effect
Setting
Convert Converts primary elements to construction elements.
to Con-
struc-
tions
Join Extends primary elements to intersection.
Ends at
Junc-
tions
To apply a tangent constraint

1. Select the Constrain Elements tool.
2. In the Tool Settings window, set Method to Smart Constrain
Elements by selecting the first icon.
3. Identify the first construction.
4. Identify the second construction.
The tangent constraint is displayed. An attempt is made to
solve and remove one degree of freedom. The acceptance
point determines which solution is selected if there are
two solutions or approximately where the solution will be
if there is a range of possibilities.
To override or force a tangent constraint, set Method to

Constrain Two Constructions to be Tangent by selecting the
second icon in the Tool Settings window.
To apply a perpendicular constraint


Constrain Elements
3. Identify the first line or ellipse.

4. Identify the second line or ellipse.
The perpendicular constraint is displayed, and the lines
are trimmed at their intersection. An attempt is made to
solve and remove one degree of freedom.
To override or force a perpendicular constraint, set Method

to Constrain Two Lines to be Perpendicular by selecting the
third icon in the Tool Settings window.
To apply a parallel constraint

3. Identify the first line or ellipse.
4. Identify the second line or ellipse.
The parallel constraint is displayed. An attempt is made to
solve and remove one degree of freedom.
To override or force a parallel constraint, set Method to

Constrain Two Lines to be Parallel by selecting the fourth
icon in the Tool Settings window.
To fix the angle of a line or ellipse

3. Identify the line or ellipse.
4. Enter a second data point on the line or ellipse.
5. Enter a third data point on the line or ellipse.
To force a line or the primary axis of an ellipse to be horizontal

or vertical, set Method to Fix Angle of Line or Ellipse by

Make Construction or Parameter Invariant
selecting the fifth icon in the Tool Settings window and set
Angle Lock to Horizontal or Vertical.
Key-in: CONSTRAIN ELEMENT
Make Construction or Parameter Invariant

Used for either of the following:
• To make a variable a constant, fixing the value of the
dimension to which it is assigned.
• To make a construction invariant (not recalculated when
solving). An invariant construction can be used in constraints.
Direct, single-element constraints, such as the radial or angle
of line dimension constraints or the location constraint, are
redundant if applied to an invariant construction.
To make a variable a constant or a

construction invariant
1. Select the Make Construction or Parameter Invariant tool.
2. Identify the construction or variable.
An attempt is made to remove the variable or curve’s
remaining degrees of freedom.
Key-in: CONSTRAIN CONSTANT
Constrain Point On Construction

Used to constrain a point (or the center of a circle or an ellipse)
to lie on a construction that is not a point, or, equivalently,
the construction to pass through a point.

Constrain Point at Intersection
To apply a point-on constraint

1. Select the Constrain Point On Construction tool.
2. Identify the construction.
3. Identify the point.
4. Reset to have MicroStation create the point.
The constraint is displayed next to the point. An attempt
is made to solve and remove one degree of freedom. The
acceptance point determines which solution is selected if
there are two solutions or approximately where the solution
will be if there is a range of possibilities.
Key-in: CONSTRAIN POINTON
In MicroStation, Construction elements do not need to be displayed

in the view when applying a point-on constraint.
Constrain Point at Intersection

Used to constrain a point to lie at the intersection of two constructions,
or, equivalently, to force two constructions to pass through a point.
The two constructions can be any kind of construction, except points. The
intersection can be a construction point or the center of a circle or an ellipse.
To apply a point-at constraint

1. Select the Constrain Point At Intersection tool.
2. Identify the first construction.
3. Identify the construction with which it is to intersect.
4. Identify the point of intersection.
or
Reset to create the point of intersection at the intersection
of the two constructions.
The intersection constraint is created next to the point of
intersection. An attempt is made to solve and remove two degrees

Constrain Two Points to be Coincident
of freedom. The acceptance point determines which solution

is selected if there are two solutions or approximately where
the solution will be if there is a range of possibilities.
Key-in: CONSTRAIN INTERSECTION
Constrain Two Points to be Coincident

Used to constrain one of the following:
• Two points to the same location (to be coincident).
• Two circles/ellipses to be concentric (have the same center).
• A point to lie at the center of a circle/ellipse.
To constrain two points to be coincident, two

circles/ellipses to be concentric, or a point
to a circle’s/ellipse’s center
1. Select the Constrain Two Points to be Coincident tool.
2. Identify the two points, circles or ellipses, or any
combination thereof.
The concentric constraint is displayed next to the point. An
attempt is made to solve and remove two degrees of freedom.
Key-in: CONSTRAIN CONCENTRIC

in the view when applying a coincident constraint.


Used to fix the location of a point (or the center
of a circle or ellipse) in the design.
To constrain a point to a location

1. Select the Fix Point at Location tool.
2. Identify the point, circle, or ellipse.
The constraint is displayed next to the point. Two degrees
of freedom are removed.
Key-in: CONSTRAIN LOCATION

in the view when applying a location constraint.
Equate Parameters or Constructions

Used to equate the endpoints of constructions. That is,
endpoints of two elements can be united, or constrained to be
equal. This tool also can be used to equate other constructions,
such as constraining two lines to be colinear.
To equate two endpoints

1. Select the Equate Parameters or Constructions tool.
2. Identify the endpoint on the first element.
3. Identify the endpoint on the second element.
4. Accept.
The two elements are adjusted to join at the identified endpoints.

Evaluate Constraints tool box
To equate two lines to be colinear

1. Select the Equate Parameters or Constructions tool.
2. Identify the first line (not at its endpoints).
3. Identify the second line (not at its endpoints).
4. Accept.
The two lines are adjusted to become colinear.
Key-in: CONSTRAIN MATCH
Construction elements do not need to be displayed in the view

when equating parameters or constructions.
Evaluate Constraints tool box

The tools in the Evaluate Constraints tool box are used to evaluate,
modify, and re-solve constraints for dimension-driven profiles.
To Select in the
tool box
Re-establish dimensions and other
constraints in a parametric profile that
has been modified with conventional
element modification tools. Re-solve Constraints
(see page 6-43)

Re-solve Constraints
To Select in the
tool box
Modify a dimension-driven profile.
Modify and Re-solve

Constraints (see
page 6-45)
See a visual representation of
relationships between constraints
in a profile.
Describe Selected
Construction or
Constraint (see
page 6-46)
Key-in: DIALOG TOOLBOX DDDMODEL OFF | ON | TOGGLE
Used to display where constraints are needed for a parametric
profile drawn with the Sketch Profile tool.
You can also use the tool to re-establish dimensions and other
constraints in a parametric profile that have been modified
with conventional element modification tools. For example,
use Re-solve Constraints if you:
• Modify a construction using the Modify Element tool or the Place

Fence tool and you want to reconstruct the design based on the
new modifications, while satisfying all constraints.
• Delete constructions or constraints and want to drop any
constructions or elements that are dependent on the deleted
elements and then re-analyze the design’s degrees of freedom.
• Copy constructions.

To re-solve constraints
1. Select the Re-solve Constraints tool.
2. Identify an element in the profile and accept.
Question marks are displayed on each vertex of an attachment
(line segment, arc, or B–spline curve) that is under-determined.
If possible, the profile is reconstructed.
If the profile cannot be reconstructed, “Not Solved” is displayed.
A diagnostic message is displayed and the symbology of
constructions and constraints may be changed.
The question marks are placed at the Active Text Size. If they
are not visible, zoom in and they will become visible. The question
marks will automatically disappear as missing constraints are
added to the profile. The total number of question mark symbols
may greatly exceed the remaining degrees of freedom in the
profile and do not necessarily represent the number of constraints
needed to make a well-defined profile. However, they often do
represent where constraints should be applied.
It may not be possible to reconstruct the model to satisfy constraints.

For example, constructions might have been modified to such an extent

Modify and Re-solve Constraints
that the solver cannot “pull them back together.” In this case, you can
choose Undo from the Edit menu to negate the changes.
All constraint placement tools activate Re-solve Constraints

automatically. Constraints can be applied to a modified design
without using the Re-solve Constraints tool.
Key-in: MODEL UPDATE
Modify and Re-solve Constraints

Used to graphically modify a dimension-driven profile. This tool
is particularly helpful in visualizing the remaining degrees of
freedom in a profile while applying constraints.
In some cases, you can manipulate the question marks interactively, or
you can manipulate attachments that are flagged by question marks to
investigate a profile’s ambiguities with Constructions turned off.
To isolate the effects of interactive manipulations and make the tool
more responsive, the Modify and Re-solve Constraints tool tries to
“freeze” as many of the model’s degrees of freedom as possible.
To modify a dimension-driven profile

1. Select the Modify and Re-solve Constraints tool.

Describe Selected Construction or Constraint
2. Identify an element in the profile.

If the message Cannot modify element is displayed, the identified
element cannot be modified with this tool.
As you move the pointer, the profile is solved and
dynamically updated.
3. Accept the modification.Reset to restore the profile as it was.
The message Not Solved is displayed if the profile cannot
be modified as requested.
If the profile is over-constrained, it may not be possible
to solve for any pointer location, and you must change
or delete constraints to modify it.
Key-in: MODEL MODIFY
Describe Selected Construction or Constraint

Used to display the name of a construction or constraint and
the names of the objects to which it is attached.
To get information about an object in a model

1. Select the Describe Selected Construction or Constraint tool.
2. Identify an element.
3. Accept the element.
The object’s number is displayed at this point. The object’s
description is displayed in the status bar.
Key-in: MODEL INFO
Each object in a model is assigned a unique name, based on its type (for
example, “Line1” for a line, “Tangent2” for a tangent constraint, and

Modify Constraint tool box
so on). Names are not unique across models. The assigned numbers
distinguish one object from another and have no other significance.
Modify Constraint tool box

The tools in the Modify Constraint tool box can be used to break or
trim constrained geometry, add fillet and chamfer constraints to
constrained geometry, and modify dimension or variable values.
To Select in the Modify

Constraint tool box
Break an element between constraints
so that additional geometry and
constraints can be inserted.
Break Constrained
Geometry (see page
6-48)
Trim two elements that share a
common intersection.
Trim Constrained
Geometry (see page
6-49)
Add a fillet between two constrained
elements.
Fillet Constrained
Geometry (see page
6-49)

Break Constrained Geometry
To Select in the Modify

Constraint tool box
Add a chamfer between two
constrained elements.
Chamfer Constrained
Geometry (see page
6-51)
Change the value of a dimensional
constraint or variable.
Modify Value of
Dimension or Variable
(see page 6-53)
Key-in: DIALOG TOOLBOX DDDMODIFY OFF | ON | TOGGLE
Break Constrained Geometry

Used to break elements between constraints in order to
insert additional geometry and constraints.
To place a break between constraints on a line

1. Select the Break Constrained Geometry tool.

Trim Constrained Geometry
2. Identify a line to break.

3. Identify a point on the line.
A constraint is placed at the point of the break.
Key-in: CONSTRAIN MODIFY BREAK
Trim Constrained Geometry

Used to trim two elements that share a common intersection.
To trim two lines that share a common intersection

1. Select the Trim Constrained Geometry tool.
2. Identify the first line of the intersection.
3. Identify the second line of the intersection, then
accept with a data point.
The section of each line that extends beyond the intersection
is trimmed, and constraints are placed at the beginning
of each line and at the intersection.
Key-in: CONSTRAIN MODIFY TRIM
Fillet Constrained Geometry

Used to add fillet constraints to a constrained profile. You can specify
the size of the fillet radius and you can name the fillet constraint.

Fillet Constrained Geometry
Tool Effect
Setting
Radius Sets the size of the radius for the fillet constraint.
Create A radius dimension will be placed with
Dimen- the fillet, when on.
sions
Con- Sets the constraint name for the fillet constraint.
straint
(dialog
setting)
To add a fillet at the intersection of two lines

1. Select the Fillet Constrained Geometry tool.
2. In the Radius field, enter the required radius.
If Create Dimensions is off, the intersecting lines are filleted
and no dimensions are created.
If Create Dimensions is on, accepting the second line of the
intersection opens the Choose Parameter Name dialog box.
5. Enter a name for the fillet constraint and click OK.
The intersecting lines are filleted, and the dimension
of the fillet radius is displayed with its name below (for
example, “rad1 = 0.5000”). If no name is entered for the

Chamfer Constrained Geometry
constraint, a generic name is given (for example “Radius23”)

and only the dimension is displayed.
Key-in: CONSTRAIN MODIFY FILLET

Used to add chamfer constraints to a constrained profile.
There are three methods for specifying the size of the chamfer
and you can name the chamfer constraint.
Tool Effect
Setting
Method Sets the placement parameters for the
chamfer constraint.
Distances—Sets (1) Distance 1, the chamfer distance
from the vertex, along the first selected surface,
and (2) Distance 2, the chamfer distance from the
vertex, along the second selected surface.
Distance and Angle—Sets (1) the chamfer Distance

from the vertex, along the selected surface, and (2) the
angle formed by the chamfer and the selected surface.
Chamfer Length—Sets the distance between the

two selected surfaces, along the chamfer.
Create When on, chamfer dimensions are placed
Dimen- with the chamfer.
sions
Distance (Method set to Distances only) Sets the chamfer
1 distance along the surface that is selected first.
Distance (Method set to Distances only) Sets the chamfer
2 distance along the surface that is selected last.
Distance (Method set to Distance and Angle only) Sets the
chamfer distance with respect to the selected surface.

Tool Effect
Setting
Angle (Method set to Distance and Angle only) Sets the
chamfer angle with respect to the selected surface.
Length (Method set to Chamfer Length only) Sets the
length along the chamfer.
Con- • (Method set to Distances) Sets the constraint
straint 1 name for the Distance 1 constraint.
(dialog
• (Method set to Distance and Angle) Sets the
setting)
constraint name for the Distance constraint.
• (Method set to Chamfer Length) Sets the
constraint name for the Length constraint.
Con- • (Method set to Distances) Sets the constraint
straint 2 name for the Distance 2 constraint.
(dialog
• (Method set to Distance and Angle) Sets the
setting)
constraint name for the Angle constraint.
To add a chamfer at the intersection of two lines

1. Select the Chamfer Constrained Geometry tool.
2. In the Distance 1 and 2 fields, enter the required values.
If Create Dimensions is off, the intersection is chamfered
with no dimensions created.
If Create Dimensions is on, accepting the second line of the
intersection opens the Choose Parameter Name dialog box.
5. Enter a name for the first constraint and click OK.
The Choose Parameter Name dialog box remains open for
you to name the second constraint.
6. Enter a name for the second constraint and click OK.
The intersecting lines are chamfered, and the dimensions are
displayed with their respective names below (for example,

Modify Value of Dimension or Variable
“cham1 = 0.5000”). If no names are entered for the constraints,

a generic name is given (for example, “Distance21”) and
only the dimensions are displayed.
Key-in: CONSTRAIN MODIFY CHAMFER
Modify Value of Dimension or Variable

Used to edit the value of a variable or dimensional constraint.
Tool Effect
Setting
Param- Sets the value of the variable or dimensional
eter constraint.
To edit the value of a dimensional constraint

1. Select the Modify Value of Dimension or Variable tool.
2. Identify the dimensional constraint.
3. Accept the dimensional constraint.
The “Parameter” field’s label changes to the name of the variable
that sets the dimensional constraint’s value.

Dimension-Driven Design dialog box
4. Key in a new value.

5. Press áTabñ or áReturnñ.
The profile is updated.
Key-in: MODEL EDIT_DIMENSION
Dimension-Driven Design dialog box

Used to place derived cells or to modify the dimensions and constants
of dimension-driven cells or derived cells — cells that are derived from
Dimension-driven Cells (see page 6-8) . A derived cell’s geometry
is defined by values entered for each dimension or constant and
the dimension-driven cell’s underlying constraints.
Dimension-Driven
Design dialog
box
Key-in: MDL LOAD DDCELL

Key-in: PLACE CELL DIMENSION
Edit
Sets the value of the dimension or constant that is
selected in the list box.
If the cell cannot be derived from the supplied dimension and constant
values, the cell is not placed, and you are prompted to enter new values.
Save Constraints (derived cell placement only)

If on, the Active Cell will be placed with active constraints,
so it can be modified after placement.

Level Structure Files
When modifying a dimension-driven (or derived) cell, you can

also specify the values by keying in RESET DIMENSION
<PARAMETER>[=]<VALUE> [<PARAMETER>[=]<VALUE> …].
PARAMETER is the name of some constant in the model (or
possibly the internal name of some dimension), and VALUE is a
numeric constant. Each assignment expression must be preceded
by a space or punctuation. The syntax permits comments enclosed
in brackets (“[]”). Upon entry of the key-in with a valid syntax,
the dimension-driven cell is solved and modified.
For more information about placing derived cells, see

To place a derived cell.
Level Structure Files

When you assign named levels to level groups, you can easily hide or
display related levels. A level structure is analogous to an operating
system’s directory structure: just as directories can contain other
directories, groups can contain other groups.
Levels are assigned to groups just as files are saved in directories.
(In fact, the Level Names dialog box displays the “path” through
the level structure to the current group or a “tree” of the groups.)
A level can be in several level groups.
Guidelines for creating a level structure

It is most efficient to define and save a level structure before
beginning to draw. A variety of sample level structures are delivered
as part of MicroStation’s workspace modules. You can save your
own level structures to use in other design files.

Level Names
dialog box
showing
the level
structure
“aiaarch.lvl,”
part of which
is shown
in the table
below.
When you create your own level structure, you can group individual
levels and groups of levels hierarchically for easy manipulation.
It is easiest to map out all hierarchical groups before defining the level
structure. MicroStation lets you define the level structure by adding
new levels and groups to existing groups. Therefore, you must create
the highest-level groups first, then create lower-level groups within
those groups, and, last, assign individual levels to existing groups.
General Procedure — To create a level structure

1. From the Settings menu’s Level sub-menu, choose Manager.
The Level Manager dialog box opens.
From the dialog box’s Options menu, choose Level Names.
From the Settings menu’s Level sub-menu, choose Names.
The Level Names dialog box opens.
2. Name the highest-level groups in the structure. See To create
the highest-level groups on page 6-57.
3. Name subordinate groups. See To create subordinate
group on page 6-58.
4. If you have not named the levels to be assigned to groups, name
them now. See Status Barin the on-line documentation.
5. Assign levels to groups. See To assign a level or levels
to a group on page 6-59.
6. Save the level structure. See To save the active design file’s
level structure in a separate file on page 6-60.

7. In the Level Names dialog box, click the Done button.
Level names and groups are settings that must be saved; choose
Save Settings from the application window’s File menu. If you do
not save settings (or save the level structure in a separate file),
when you close the design file, the level structure is lost.
To create the highest-level groups

1. From the Level Names dialog box’s Display menu,
choose Group Operations.
The controls for group operations are displayed in the
Level Names dialog box.
Level Group
dialog box
The Level Group dialog box opens.

3. In the Level Group dialog box, key in a unique (not already
used) name of up to 16 characters for the group.
The group name is shown in the Level Names dialog
box’s Group list box (or if you are using Level Manager
(Settings > Level > Manager), the group name is shown in
the Group list box on the Groups tab page after you click
Done in the Level Names dialog box).
5. Repeat steps 1–4 until all the highest-level groups are shown
in the Group list box. Do not select any of the group names;
keep the “-/” symbol selected. (Otherwise a new group is
a sub-group of the selected group.)

To create subordinate groups

A “tree” of the group structure is shown in the Group list box. The
“root” is designated by a backslash (“\\xd3 ) symbol.
Any group in the tree (including the root) can be expanded
or collapsed. To expand a group, double-click it. All the
sub-groups within it (that are not collapsed) are displayed
below it, and a minus sign (“-”) is displayed in front of the
group’s name. Double-clicking also collapses a group. All
sub-groups of that group are hidden and a plus sign (“+”)
is displayed before the group’s name.
2. In the Group list box, select the name of an existing group.
The Level Group dialog box opens.
4. In the Name field, key in a unique (not the name of a sub-group of
the selected group) name of up to 16 characters.
The group name is shown in the Level Names dialog
box’s Group list box (or if you are using Level Manager
(Settings > Level > Manager), the group name is shown in
the Group list box on the Groups tab page after you click
Done in the Level Names dialog box).
To remove a group
A “tree” of the group structure is shown in the Group list box.
2. In the Group list box, select the name of the desired group.
3. Click the Delete button.
An alert box is displayed, warning you that deleting the level
group deletes all sub-groups and level names within it.
4. In the alert box, click the OK button.

To assign a level or levels to a group

choose Level Operations.
The controls for level operations are displayed in the
Level Names
dialog box
with controls
for level
operations.
2. In the list box, select a single level by clicking it.

3. Select multiple levels by control-clicking (holding down
the áCtrlñ key while clicking) them.
4. Select a range of levels by clicking (or control-clicking, if others
are already selected) the level at one end of the range, then
shift-clicking (holding down the áShiftñ key while clicking)
the level at the other end of the range.
If a level is currently assigned to more than one level, it
appears more than once in the list box. You can select
any instance of the desired level.
5. Click the Group button.
The Select Target Group dialog box opens.

Select Target
Group dialog
box
6. To assign the selected level(s) to a group without removing

them from any group they are already assigned to, click
the Copy to Group button.
7. To assign the selected level(s) to a group and remove them from
the group to which (the selected instance(s) of) the level(s) are
already assigned, click the Move to Group button.
To remove a level from a group

choose Level Operations.
The controls for level operations are displayed in the
2. In the list box, select the desired level name and number.
If a level is currently assigned to more than one group, it
appears more than once in the list box. If this is the case,
select the instance of the level that is assigned to the group
from which it is to be deleted. (Refer to the information at right
side of the list box under the label “Group.”)
To save the active design file’s level structure

in a separate file
1. From the Level Names setting box’s File menu, choose Save.
The Save Level Structure dialog box opens. By default, level
structure files are given the extension “.lvl” and are stored
in the active workspace’s “data” directory.

Color Tables
2. In the Name field, key in a name for the level structure file.
Color Tables
An element’s color attribute is stored with the element in the design
file as a number in the range 0-254. The design file color table
determines the correspondence between the 255 color attribute
values and display colors. For example, if according to the design
file color table color number 3 corresponds to red, elements with
a color attribute of 3 are displayed in red.
You can attach a color table to a design file. If a design file has a color
table attached, the color table is opened (and its colors used to display
elements) each time the design file is opened. Color tables can be
customized and saved in color table files for subsequent attachment to
multiple design files. (See Customizing a Color Table on page 6-62.)
If a design file does not have a color table attached, its color
table is the MicroStation system default color table. The Default
Color Table configuration variable (MS_DEFCTBL) in the
Configuration dialog box of the Workspace menu specifies the
default color table so it too can be customized.
Balanced colors
MicroStation uses balanced colors to represent colors in the
design file. Balanced colors are a representative spread of colors,
evenly spaced across the color spectrum. Colors of elements in
the design file are mapped to the colors that the hardware can
display using a “closest match” algorithm.
• If the display hardware supports many colors, then a large

balanced color table can be constructed and the colors of elements
in the design file can be accurately represented on screen.
• If the display hardware supports only a few colors (especially
16 or less), then a smaller number of balanced colors must be
spread more thinly across the spectrum — this may cause some
colors to be less accurately represented on screen.
The benefits of balanced colors are:

Balanced colors
• Display hardware that supports a small number of colors can be

made to seem to have many more colors than it actually does.
• Elements in reference files that have their own color
tables can be matched to the balanced colors to more
accurately represent their colors.
• Balanced colors allow MicroStation to create realistic renderings of
3D models regardless of the number of colors in the design file,
even on hardware that supports a limited number of colors.
General Procedure — To customize a color table

1. From the Settings menu, choose Color Table.
The Color Table dialog box opens.
Color Table
dialog box
2. If the attached color table (or the default color table if none is
attached) is not the color table you want to customize, open a
color table file or retrieve the default color table. From the File
menu in the Color Table dialog box, choose Open to open a color
table file or Default to retrieve the default color table.
In the former case, the Open Color Table dialog box opens. It
is operated like the Open Design File dialog box.
3. (If opening a color table file,) select a file in the Open Color
Table dialog box and click the OK button.
4. Use the controls in the Color Table dialog box:

Balanced colors
To interpolate colors (see page 6-63)

To duplicate a color elsewhere in the table (see page 6-64)
To individually modify a color (see page 6-64)
5. When done customizing the colors, choose Save As from the

File menu in the Color Table dialog box.
The Save Color Table dialog box opens. It is operated like
the Save Design As dialog box.
6. Use the Save Color Table dialog box to save the color
table in a color table file.
7. To attach the custom color table to the active design file and close
the Color Table dialog box, click the Attach button.
or
To simply close the dialog box, click the Cancel button.
To interpolate colors
1. From the Edit menu in the Color Table dialog box,
choose Interpolate Colors.
The Color Interpolation dialog box opens.

Balanced colors
2. From the Interpolation Style option menu, choose RGB (Red,

Green, Blue) or HSV (Hue, Saturation, Value).
3. Turn on Start Color and select the starting color by
clicking it in the color palette.
4. Turn on End Color and select the ending color by
clicking it in the color palette.
5. To start interpolation, click the Blend button.
6. (Optional) — Repeat steps 2–5 for other color ranges.
7. Click the OK button to accept the color table modifications

and return to the Color Table dialog box.
During this procedure, you can double-click colors to manually

modify them using the Modify Color dialog box (see To
individually modify a color on page 6-64).
To duplicate a color elsewhere in the table

1. In the Color Table dialog box’s color palette, select the
color you want to duplicate.
2. From the dialog box’s Edit menu, choose Copy Color.
3. Select the color you want to replace with the duplicate
of the copied color.
4. From the dialog box’s Edit menu, choose Paste Color.
To individually modify a color

1. In the Color Table dialog box’s color palette, select the
color and click the Change button.
or
In the color palette in the Color Table dialog box or the Color
Interpolation dialog box, double-click the color.
The Modify Color dialog box opens.

Line Style Libraries
2. Use the controls in the Modify Color dialog box to adjust the color.
Line Style Libraries

Line style libraries contain custom line style definitions. A
line style definition consists of a name and one or more Line
style components (see page 6-67) .
Copying Line Style Definitions

Line style definitions are copied from source line style libraries
to destination line style libraries. The source line style library
is the file that contains the line style definitions you want
to copy, and the destination line style library is the file to
which you copy the selected definitions.
To copy line style definitions from one line

style library to another
1. From the Primary Tools tool box’s Line Style option
menu, choose Edit.
The Line Style Editor dialog box opens.

Copying Line Style Definitions
2. From the File menu, choose Open.

The Open Line Style Library dialog box opens. (You can also
use File > New to create a new line style library.)
3. In the File list box, select the file you want to be
the line style library.
4. Click OK.
The Line Style Editor dialog box displays relevant information on
the line styles contained in the selected line style library.
Once you have a line style library file assigned, you can then
select then the source and destination files.
5. From the Line Style Editor’s File menu, choose Manage.
The Manage Line Style Definitions dialog box opens listing
the line styles in the current line style library.
Manage
Line Style
Definitions
dialog box
6. From the File menu, choose Open Source File.

The Select Source Line Style Library dialog box opens.
7. In the File list box, select the name of the file that you
want to be the source file (the file from which you want
to copy line styles), and click OK.
The filename and list box on the left contain the source entries;
and the filename and list box on the right contain the destination
entries. You can copy line styles from the source file into the
destination file, rename the line styles in this file, and delete line
style resources from this file. The resource file is open only for
reading and copying line styles into another file; the original
resource file is not modified by copying styles from it.

Line style components
8. Select the name of the line style definition you want

to copy in the source list box.
9. Click Copy.
or
Drag the line style name over to the Destination list box and drop it.
The line style name appears at the bottom of the
Destination line style name list.
10. Click OK.
You can copy line styles from more than one source file in the
destination file at one time by using File > Open Source File.
You may also open more than one destination file to add styles
as well, by using File > Open Destination File. If you have
made changes to the current destination file, you will be
prompted to save them before continuing.

A line style component is a component of a line style
definition. The line style library, “lstyle.rsc,” installed in
Bentley’s “Workspace\system\symb” directory contains many
sample line style definitions.
The line style component types are stroke patterns, point

symbols, and compound components.
Stroke pattern
A stroke pattern is a pattern of dash strokes and gap strokes that is
displayed repeatedly along the length of an element. For each dash
stroke, the length and optionally, the color and width, are specified.
Stroke pattern attributes

The following are stroke pattern attributes:
• Shift (the relationship between the stroke pattern, the first

stroke, and the beginning and end of the element).

• Whether the stroke pattern is truncated and restarted for each

element segment (displayable vector) or continued across segments.
• The number of repetitions of the stroke pattern used

to display elements.
Stroke attributes
The following are stroke attributes:
• Whether the stroke is a dash stroke or a gap stroke.
• Length, in master units.
• Whether the length is fixed or variable (subject to scaling).
• Whether the stroke is displayed with width and if so,

which half or halves.
• Starting and ending width, in master units.
• The type of end cap (if any).
• Whether the stroke can be broken at element vertices.
Point symbol
A point symbol defines how a series of point symbols (like shared
cells) are displayed along the length of an element. A point symbol
component contains an association to a stroke pattern component from
which dash stroke information is extracted to place the point symbols.
A point symbol is a named group of elements, much like a shared

cell, that includes the following information:
• An association to the stroke pattern on which the

component is based.
• Associations between point symbols and strokes in
the base stroke pattern.

• How point symbols are justified on strokes.

• Optional offset, rotation, and scale factors.
Compound
A compound component is a combination of components of any
type. Compound components can be nested. The only way to
display both dash strokes and point symbols along the length of
an element is to create a compound component.
For each component specified in a compound component, an offset is

specified. The offset value specifies the distance (perpendicularly) from
the working line to where the component is displayed. Offsets can be
used to produce many of the effects available with multi-lines.
General Procedure — To define a line style

1. From the Primary Tools tool box’s Line Styles
sub-menu, choose Edit.
The Line Style Editor dialog box opens.
Line Style
Editor dialog
box

2. From the dialog box’s File menu, choose New to create a line style
library or Open to open an existing line style library.
The Create Line Style Library dialog box or the Open Line Style
Library dialog box opens. The controls are analogous to the Create
Design File and Open Design File dialog box, respectively.
3. Use the dialog box to create or open a line style library.
When you close the dialog box, focus returns to the
Line Style Editor dialog box.
4. Create or modify a line style. See one of the following sections:
Working with stroke pattern components

(see page 6-71)
Working with point symbol components
(see page 6-76)
Working with compound components (see page 6-81)
5. From the Edit menu’s Create sub-menu, choose Name.

A line style named “Unnamed” is inserted in the Styles
list box and is automatically selected. If a component is
selected in the Components list box, >> is displayed next to
the component’s type to indicate the component is directly
linked to the new line style definition. (If the component is
a compound component, its sub-components are part of the
definition — in essence, indirectly linked.)
If a component is not selected, the new line style is linked
by default to the Default solid line internal stroke pattern
component. To select and link a different component, see
To change the component to which a line style definition
is directly linked on page 6-71.
6. In the Name field below the Styles list box, key in the
line style name (replace “Unnamed”).
The specified name replaces “Unnamed” in the Styles list box.
7. From the File menu in the Line Style Editor dialog
box, choose Save.

To change the component to which a line style

definition is directly linked
1. In the Line Style Editor dialog box’s Components list
box, select the desired component.
2. From the dialog box’s Edit menu, choose Link.
3. From the dialog box’s File menu, choose Save.

Here are procedures for creating, modifying, and deleting
stroke pattern components.
In some cases, the most efficient way to create a stroke pattern

component is to adapt an existing component by duplicating
it and then modifying the duplicate.
To create a stroke pattern component (by

adapting an existing component)
1. In the Components list box, select the stroke pattern
component to adapt.
The controls for working with stroke patterns are displayed.
Controls for
working with
stroke pattern
components
in Line Style
Editor dialog
box

2. From the Edit menu, choose Duplicate.

The component is duplicated. The duplicate is automatically
selected in the Components list box, and a sample
line with the stroke pattern component and the Stroke
Pattern itself are displayed.
3. (Optional) — For each stroke you want to delete from the
duplicate, select the stroke, and click the Delete button.
To select a stroke, click the stroke in the Stroke Pattern
display. The selected stroke is highlighted.
4. (Optional) — For each stroke you want to add, click the Add button.
Each stroke is added to the (right) end of the Stroke Pattern as a
gap stroke, which is indicated with an unfilled bar.
5. (Optional) — For each stroke you want to change from a

gap stroke to a dash stroke, select the stroke and choose
Dash from the Stroke Type option menu.
Each dash stroke is indicated with a filled bar. The resulting stroke
pattern component is displayed above the stroke pattern display.
6. (Optional) — Set other stroke attributes.

To permit the length of the selected stroke to be adjusted
when the stroke pattern is fractionally shifted or repeated
a fixed number of times, choose Variable from the Length
option menu. Otherwise, choose Fixed.
To change the length of the selected stroke, key in the length, in
master units, in the Length field. You can also change the length
of a stroke by dragging its handle, which is located in the Stroke
Pattern display above or below the ending point of the stroke.
To set the type of end cap to be displayed on the selected stroke
when the stroke is displayed with width, choose the desired
end cap type from the Dash Caps option menu.

Dash Caps
(from top):
Arc, Closed,
Extended,
Hexagon,
Open
To cause the selected stroke to break at element vertices, choose

Break from the Corners option menu. Otherwise, choose Bypass.
Corners:
Break,
Bypass
To display the selected stroke with width, choose Full

from the Width option menu.
or
To cause only the left or right half of the stroke to be displayed
(with width), choose Left or Right from the Width option menu.
or
To display the stroke without width, choose None from
the Width option menu.
Width: Full,
Left
If the selected stroke is a dash stroke that is set to display

with width, to set the stroke’s start and end width, key in the
widths, in master units, in the Start and End fields. To taper
the stroke, set Start and End to different values.
7. (Optional) — Set stroke pattern attributes.

To set the fraction of the first stroke that is displayed at the start
and end of an element (or element segment) displayed using

this stroke pattern, choose Fraction from the Shift option menu
and key in the desired fraction, in decimal, in the field.
To set the distance, in master units, that the stroke pattern
is shifted relative to the beginning of an element (or element
segment), choose Distance from the Shift option menu, and key
in the desired distance, in master units, in the field.
To set the number of repetitions of the stroke pattern along the
length of an element (or each segment), choose Count from the
Repetitions option menu and key in the desired number in the field.
To cause the stroke pattern to repeat continuously along the
length of an element (or each segment), choose Unlimited
from the Repetitions option menu.
To truncate and restart the stroke pattern for each element
segment (displayable vector), turn on Single Segment.
To continue the stroke pattern across element segments,
turn off Single Segment.

Effect of Shift
settings based
on dash and
gap at top:
Distance =
0.0 (top);
Distance =
0.2 (center);
Fraction =
0.5 (bottom)
8. (Optional) — In the field below the Components list box,

key in the component description.
9. From the File menu in the Line Style Editor dialog box, choose Save.
To create a stroke pattern component (without

1. From the Edit menu’s Create sub-menu, choose Stroke Pattern.
A new, blank row is inserted and is automatically selected
in the Components list box. The controls for working with
stroke patterns are displayed.
2. Follow the steps in To create a stroke pattern component (by
adapting an existing component) (see page 6-71) , beginning
with step 4. Steps 4 and 5 are not optional.
To modify a stroke pattern component

component to modify.
The controls for working with stroke patterns are displayed,
along with a sample line with the stroke pattern component
and the stroke pattern itself.
2. Follow the steps in To create a stroke pattern component
(by adapting an existing component) (see page 6-71)
, beginning with step 3.

To delete a stroke pattern component

component to delete.
A sample line with the stroke pattern component and the
stroke pattern itself are displayed.
2. From the Edit menu, choose Delete.

The following are procedures for creating, modifying, and deleting
point symbol components, and creating a point symbol.
In some cases, the most efficient way to create a point symbol

To create a point symbol component (by

1. In the Components list box, select the point symbol
component to adapt.
The controls for working with point symbol components
are displayed.


selected in the Components list box, and a sample line with
the point symbol component, the base stroke pattern, and
the point symbol itself are displayed.
3. (Optional) — Click the Base Stroke Pattern button.
The Base Stroke Pattern dialog box opens.
Base Stroke
Pattern
dialog box
4. (Optional) — In the Base Stroke Pattern dialog box, select

a stroke pattern component on which to base the new
point symbol component, and click the OK button (or
double-click the desired component).
5. (Optional) — Back in the Line Style Editor dialog box, select

the stroke with which you want to associate a point symbol
by first having the desired Point Line Style displayed.
Then, click the Select button at the bottom of the dialog
box in the stroke pattern display.
The selected stroke is highlighted.
6. (Optional) — Click the Select Symbol button.

The Select Point Symbol dialog box opens. All point symbols
in the open line style libraries are available for selection. To
create additional point symbols and make them available for
selection, see To create a point symbol on page 6-80.

Select Point
Symbol dialog box
7. (Optional) — In the Select Point Symbol dialog box, select

a point symbol, and click the OK button (or double-click
the desired point symbol).
Back in the Line Style Editor dialog box, the resulting point
symbol component is displayed below the list boxes.
8. (Optional) — Specify the association between the point

symbol and the selected stroke:
To put the origin of the associated point symbol on the midpoint
of the stroke, choose Center from the Origin option menu.
or
To put the origin of the associated point symbol on the
starting point (left end) of the stroke, choose Left from
the Origin option menu.
or
To put the origin of the associated point symbol on the ending point
(right end) of the stroke, choose Right from the Origin option menu.
To specify an additional point symbol origin horizontal offset
distance (from the justification point set on the stroke in the
previous step), key in the desired distance, in master units in the
direction of the stroke pattern (x-axis), in the X Offset field.
To specify an additional point symbol origin vertical offset distance
(from the justification point on the stroke), key in the desired

distance, in master units in the direction perpendicular to the

stroke pattern (x-axis) and its plane, in the Y Offset field.
To set the point symbol rotation angle, key in the desired
angle, in degrees, in the Rotation field.
9. (Optional) — Repeat steps 5-8 to associate point symbols

with additional strokes.

To create a point symbol component (without

1. From the Edit menu’s Create sub-menu, choose Point.
in the Components list box. The controls for working
with point symbols are displayed.
with step 3. Steps 3-8 are not optional.
To modify a point symbol component

The controls for working with point symbols are displayed,
along with a sample line with the point symbol component,
the base stroke pattern, and the point symbol itself.

To delete a point symbol component

A sample line with the point symbol component, the base stroke
pattern, and the point symbol itself are displayed.
To create a point symbol

1. Draw the elements that will be part of the point symbol.
2. Select or fence the elements. If you use the fence, the
Fence (Selection) Mode is ignored; only elements completely
enclosed by the fence are used.
3. (Optional) — Use the Define Cell Origin tool (see the Using Cells
chapter in the User’s Guide) to define the point symbol origin.
4. In the Components list box, select any point symbol component.

The controls for working with point symbol components
are displayed.
5. Click the Create button.
The Create Point Symbol dialog box opens.
6. In the Name field, key in a name for the symbol. The
maximum number of characters in a valid symbol name
is 16; spaces are not permitted.
8. If you skipped step 3, enter a data point to define
the point symbol origin.
If a point symbol with the same name is already present in the

library, an alert box containing that information is displayed,
and you are given the option of overwriting the existing
point symbol or cancelling creation.

Working with compound components

Here are procedures for creating, modifying, and deleting
compound components.
In some cases, the most efficient way to create a compound

To create a compound component (by adapting

an existing component)
1. In the Components list box, select the compound
component to adapt.
The controls for working with compound components are displayed.
Controls for
working with
Compound
components
in Line Style
Editor dialog
box

selected in the Components list box, and a sample line with
the compound component is displayed.
3. (Optional) — For each sub-component you want to remove from
the duplicate, select the sub-component in the Sub-Components
list box, and click the Remove button.
4. (Optional) — To insert a sub-component, click the Insert button.

The Select Component dialog box opens.

Select
Component
dialog box
5. (Optional) — In the Select Component dialog box, select

a component, and click the OK button (or double-click
the desired component).
Back in the Line Style Editor dialog box, the component is
listed in the Sub-Components list box.
6. (Optional) — Repeat steps 3-4 to insert additional sub-components

in the new compound component.
As you insert additional sub-components, a sample line
with the resulting compound component is displayed
above the sub-components list box.
7. (Optional) — To cause a component to be displayed parallel

to the work line, select the component in the Sub-Components
list box. Then, in the Offset field, key in the desired offset
distance, in master units measured perpendicular to the work
line. Repeat for additional components as desired.


Technical background
To create a compound component (without

1. From the Edit menu’s Create sub-menu, choose Compound.
in the Components list box. The controls for working with
compound components are displayed.
with step 4. Steps 4 and 5 are not optional.
To modify a compound component

The controls for working with compound components are
displayed, along with a sample line with the compound component.
To delete a compound component

A sample line with the compound component is displayed.
Technical background
The attribute data section of an element placed with a line style
contains a name ID plus any line style modifiers specified in the Line
Styles dialog box. The name ID identifies only the name of the line
style in an ID-to-Name map that is contained in the design file. This
name is used to obtain the resource type and ID of each line style

Settings Files
component in the line style definition based on a Name-to-Resource

ID map that is stored in the line style library, which is a resource
file along with the component definitions themselves.
The name indirection is necessary to avoid the need for unique

component resource IDs across many different line style libraries. It
also provides a simple method for replacing line styles for different
display options. Line styles can be completely replaced simply by
changing line style libraries, provided the new line style library
contains a compatible Name-to-Resource ID map. (Line style libraries
are binary-compatible across all MicroStation platforms.) The
indirection also makes it possible for a single line style component
to be contained in multiple line style definitions.
Settings Files
Of all the types of module data, settings files (“.stg” files)
affect the broadest range of MicroStation operations and
are most dependent on your organization’s design standards
and specifics of individual projects.
Settings files contain settings groups which in turn contain settings
group components. For information about using already defined
settings groups and their components, see Using the Select Settings
Window in the Placing Elements in 2D chapter of the User’s Guide.
This section describes how to create and modify settings files,

settings groups, and settings group components. The Edit Settings
dialog box is used to perform these functions.
To open the Edit Settings window

1. From the Settings menu, choose Manage.
The Select Settings window opens.
The listed settings groups and components are stored in the
open settings file; its filename is shown in the title bar.
2. From the Select Settings window’s File menu, choose Edit.

Creating settings files
Edit Settings
dialog box

Because settings group components refer to other types of module data
such as cell libraries and custom line styles, you will likely want to
create your own settings files. Although you can create settings files
“from scratch,” it is easier to modify a copy of an existing settings file.
The sample workspace settings files are excellent examples and starting
points for customization. They are installed in workspace “data”
directories — for example, “Workspace\system\data\styles.stg”. Use
your system’s file copying function to make a copy of a settings file. The
Edit Settings dialog box contains controls that make it easy to duplicate
settings groups and individual components in an existing settings file.
To create a settings file “from scratch”

1. From the Edit Settings dialog box’s File menu, choose New.
The Create New Settings File dialog box opens.
2. Use the Drives option menu and Directories list box to
specify the destination directory. See Modifying the Project
Configuration File on page 6-96.

3. In the Files field, key in the desired filename.

The focus returns to the Edit Settings dialog box. The title bar
shows the name of the new settings file indicating that the file is
open for the creation and maintenance of settings groups.
To duplicate a settings group or component

1. From the Category option menu in the Edit Settings dialog
box, choose the category — Drawing, Scale, or Working Unit
— to which the settings group (or the “parent” settings
group of the component) belongs.
2. In the Group or Component list box, select the settings
group or component to duplicate.
3. From the dialog box’s Edit menu, choose Duplicate.
You can also create settings files from settings group specifications
stored in text files using the ASCII Group utility.
General Procedure — To create a settings

group “from scratch”
1. From the Category option menu in the Edit Settings dialog
box, choose the desired settings group category — Drawing
(the default), Scale, or Working Units.
2. If the open settings file, identified in the title bar, is not
the file in which you want to create the settings group, then
you must create or open the desired file. From the File
menu in the Edit Settings dialog box, choose New to create
a file or Open to open an existing file.
The Create Settings File dialog box or the Open Settings File
dialog box opens. The controls are analogous to the Create Design
File and Open Design File dialog box, respectively.
Use the dialog box to create or open a settings file.
When you are done, focus returns to the Edit Settings dialog box.

3. From the Edit menu’s Create sub-menu, choose Group.

A new group, Unnamed, is added to the Group list box
and automatically selected.
4. In the field below the Group list box, key in a
meaningful group name.
5. If the group is a Scale or Working Units settings group, define
its settings (see To define or modify the settings in a scale
settings group on page 6-87 or To define or modify the settings
in a working units settings group on page 6-87).
or
If the group is a Drawing settings group, define its components
(see Defining a Drawing Component on page 6-88).
To define or modify the settings in a

scale settings group
1. From the Category option menu in the Edit Settings
dialog box, choose Scale.
2. In the Group list box, select the desired group.
3. From the Edit menu in the dialog box, choose Modify.
The Edit Scale dialog box opens.
Edit Scale
dialog box
4. Use the fields and option menus to specify the relationship

between paper units and drawing units.
To define or modify the settings in a working

units settings group
dialog box, choose Working Unit.

2. In the Group list box, select the desired group.

3. From the Edit menu in the dialog box, choose Modify.
The Edit Work Units Group dialog box opens.
Edit Work
Units Group
dialog box
4. From the Master Units option menu, choose the

desired master units.
5. From the Sub Units option menu, choose the desired sub-units.
6. In the Pos Units Per Sub-Unit field, key in the number
of positional units per sub-unit.
General Procedure — To define a drawing

component
1. Locate an element whose attributes you want to match in the
component definition, and remember its location.1
2. If you are defining a Cell component2 and you will want the active
scale factors to be automatically adjusted when the component is
selected in the Select Settings window, check for the existence of
an appropriate working units settings group(s) and, optionally, an
appropriate scale settings group(s). For more information about
1 The general procedure for modifying an existing drawing component is similar.
Only steps 5-6 are unique to the creation procedure, and steps 1, 8, and 9 are
optional in the modification procedure.
2 Actually, a Cell component or an Active Point or Area Pattern component that will specify a cell.

scale and working units settings groups, consult the following

table and refer to the cross-referenced section.
Group type For background For the

information, see definition
procedure, see
Scale “Scale settings “To define or modify
groups”in the the settings in
Placing Elements a scale settings
in 2D chapter of group” on page 6-87
the User’s Guide
Working Units “Working units “To define or modify
settings groups”in the settings in
the Placing a working units
Elements in 2D settings group” on
chapter of the page 6-87
User’s Guide

dialog box, choose Drawing.
4. In the Group list box, select the group to which the
component belongs.
5. From the Edit menu’s Create sub-menu, choose the type of
component you want to create — Active Point, Area Pattern,
Cell, Dimension, Linear, Multi-line, or Text.
A new group, Unnamed, is added to the Component list
box and automatically selected.
6. In the field below the Component list box, key in a
meaningful component name.
7. In the Component list box, double-click the component.
or
From the Edit menu, choose Modify.
A Modify component dialog box opens in which you can
define the component’s settings.

Modify
component
dialog box
(Linear
component
type)
8. Click the Match button.

9. Identify an existing element attributes will serve as the
basis for the component’s settings.
The controls in the Modify component dialog box update
to reflect the attributes of the identified element. The
check box settings are not affected.
10. Turn on the check boxes that directly correspond to active settings
— Level, Color, (Line) Style, (Line) Weight, (Active) Angle, (Active)
Cell, (Active) Scale, etc. — that you want to be automatically
adjusted when the component is selected in the Select Settings
window. For example, if you want the Active Color to be
automatically set when the component is selected (to the color of
the element you identified in step 9), turn on the Color check box.
11. To fine-tune the matched settings, use the fields
and option menus.
12. If the component type is Text (or Active Point and the element
you identified in step 9 is a text element) and you want the
active text size and spacing settings to be automatically
adjusted when the component is selected, specify the manner
in which text is to be sized and spaced. See To specify
text sizing and spacing on page 6-91.
or
If the component type is Dimension or Multi-line, select the
dimension or multi-line style. See To select a dimension
or multi-line style for a component on page 6-92. (For
information about defining styles, see Defining dimension
and multi-line styles on page 6-93.)


The Modify component dialog box closes and focus returns
to the Edit Settings dialog box.
It is possible, although not as easy, to define a drawing settings

group component without using the element attribute matching
capability (Match button, step 8).
To specify text sizing and spacing

1. (Optional) — To adjust the text sizing and spacing settings upon
text placement as specified in the active scale settings group
(number of paper units per design file master unit), turn on
Use Paper Size in the Modify component dialog box.
For example, if text Height is set to 1/8" and Use Paper Size
is on, the Active Text Height is adjusted to produce a plotted
height of 1/8". For a drawing scale of 1/8" = 1’, the text height of
an element placed with this component would be 1’.
Size and Spacing

section of Modify
Text component
dialog box
2. (Optional) — To ensure that text will be plotted with a

certain height, choose the units in which size and distance
are specified from the Units option menu.
For example, if text must be plotted with a height of 1/8", text
height can be set to 0.125 and Units set to Inches. The design
can then have master units of feet or meters and text will be
sized for plotting — 1/8" tall — regardless.
3. Turn on the check boxes in the Size and Spacing section for
the active text settings that you want to be automatically
adjusted when the component is selected.

Cell scaling
To select a dimension or multi-line style

for a component
1. In the Modify Dimension or Modify Multi-line dialog
box, click the Select button.
The Select Dimension (or Multi-line) Definition dialog box opens.
Select Dimension
Definition dialog
box
2. In the list box, select the desired style.

3. Click OK.
Cell scaling
The manner in which selecting a cell component3 in the Select Settings
window affects the active scale factors takes the cell library’s working
units settings and optionally, the active scale settings group, into
account. (Using the Match button in the Modify component dialog box
matches the default scale factors to an existing cell. See Defining
a Drawing Component on page 6-88, steps 2 and 8.)
3 Actually, a Cell component or an Active Point or Area Pattern component that specifies a cell.

Defining dimension and multi-line styles
To specify cell scaling

1. In the X field in the Scale section of the Modify component
dialog box, key in default horizontal scale factor.
Scale section of
the Modify Cell
component dialog
box
2. In the Y field, key in the default vertical scale factor.

3. In the Z field, key in the default depth scale factor.
4. From the Cell Work Units option menu, choose the working units
used to create cells. (The option menu items correspond to working
units settings groups defined in the open settings file.)
For cell placement, the default scale factors will be automatically
adjusted by the ratio of the active design file’s working units
to the cell library’s working units. For example, if a cell was
created with the units ft:10:100 (1000 UORs/ft.) and the
current units are ft:12:8000 (96,000 UORs/ft.), the default
scales are adjusted by a factor of 96.
5. (Optional) — To adjust the default scale factors upon cell
placement as specified in the active scale settings group (number
of paper units per master unit), turn on Apply Drawing Scale.
For example, in a metric design with a scale 1:100, there are
100 master units to 1 paper unit. In this case the default scale
factors would be adjusted by 100.0. If you are working on
a design with a scale of 1"=100’ then the adjustment factor
would be 1200.0 (1" on paper = 1200" on the design plane).
Likewise, if the scale is 1/4" = 1’ the adjustment factor would
be 48.0 (1" on paper = 48" on the design plane).

It is necessary to define a dimension or multi-line style before selecting
it as the basis for a Dimension or Multi-line settings group component.

To define a dimension style

1. Use the Dimension Settings dialog box (Element menu >
Dimensions) to adjust Dimension Settings as desired.
2. From the Edit Settings dialog box’s Style menu, choose Dimension.
The Edit Dimension Styles dialog box opens.
Edit Dimension
Styles dialog box
3. Click the Get Active button.

The style is created. It is assigned a Name and Description
each beginning with “Dim” and ending with one or more
numeric characters. The list box entry for the new style
is automatically selected.
4. In the Name field, key in a meaningful style name.
5. In the Description field, key in a meaningful description.
To define a multi-line style

1. Use the Multi-lines dialog box (Element menu > Multi-lines) to
define a multi-line as desired. See To define a multi-linein the
Advanced 2D Drafting Techniques chapter of the User’s Guide.
2. From the Edit Settings dialog box’s Style menu, choose Multi-Line.
The Edit Multi-line Styles dialog box opens.

Edit Multi-line
Styles dialog box
3. Click the Get Active button.

The style is created. It is assigned a Name and Description
each beginning with “Mline” and ending with one or
more numeric characters. The list box entry for the new
style is automatically selected.
4. In the Name field, key in a meaningful style name.
5. In the Description field, key in a meaningful description.
To delete a dimension style definition

1. From the Edit Settings dialog box’s Style menu, choose Dimension.
The Edit Dimension Styles dialog box opens.
2. In the list box, select the style you want to delete.
To delete a multi-line style definition

1. From the Edit Settings dialog box’s Style menu, choose Multi-Line.
The Edit Multi-line Styles dialog box opens.
2. In the list box, select the style you want to delete.

Modifying the Project Configuration File
Modifying the Project Configuration File

The project configuration file is a text file, which you can edit
using any word processor or text editor. See Configuration
Variable File Syntax page 3-40.
This table shows which project configuration variables
specify which parts of a module.
Module Project configuration variable

component
Design files MS_DEF (Design Files)
MS_RFDIR (Reference Files)
Seed design files MS_SEEDFILES (Seed File Location)
and drawing sheet MS_DESIGNSEED (Default Design
files File Seed)
MS_CELLSEED (Default Cell
Library Seed)
MS_SHEETSEED (Drawing Sheet
Seed File)
Cell libraries MS_CELL (Cell Library Directories)
MS_CELLLIST (Cell Library List)
Level structure MS_LEVELNAMES (Level Names)
files
Color tables MS_DEFCTBL (Default Color Table)
Font libraries MS_SYMBRSRC (Symbology Resources)
Function key MS_FKEYMNU (Function Key Menu)
menus
Line style libraries MS_SYMBRSRC (Symbology Resources)
Settings files MS_SETTINGS (Settings Resource)
MS_SETTINGSDIR (Settings Directory)
Material table MS_MATERIAL (Material Palettes)
files (and other MS_PATTERN (Pattern Maps)
files associated MS_BUMP (Bump Maps)
with rendering MS_IMAGE (Images)
and images) MS_SHADOWMAP (Shadow Maps)
Tag set libraries MS_TAGOUTPUT

Archiving: Bundling Module Data Files
Module Project configuration variable

component
Tag report MS_TAGTEMPLATES (Tag Templates)
template files
Glossary files MS_GLOSSARY (Glossary Terms)
You are not required to set these configuration variables at the Project
level. The above table is intended as a recommendation. Depending
on site or workgroup requirements, it may be preferable to set some
or all of these configuration variables at the Site or User level.
The configuration variables for digitizing tablet menus (MS_MENU)

and tutorial cell libraries (MS_TUTLIB) can be set at the
system level using the syntax explained in Configuration
Variable File Syntax on page 3-40.
Archiving: Bundling Module Data Files

Archiving provides a way of bundling a design file with the module
data files necessary to display and inter-operate with the design
file. Available from the Utilities menu, the Archive dialog box
allows you to create new archives, add to existing ones, and restore
design data, including all of the supporting resources.
Archive dialog box
Overview of the Archive utility

There are two distinct functions performed by the Archive utility:
resource identifier and archive utility with file compression. As

an archive identifier, the Archive utility allows you to select

and bundle together the design files you wish to archive, along
with all the resources needed to recreate those design files on a
different computer system. As an archiver, the Archive utility
can archive the following classes of resources:
• Design files
• Reference files
• Raster Reference files
• Cell libraries
• Background files (raster images)
• Resource files (fonts, line styles, etc.)
• Material tables
• Material tool boxes
• Materials
• Pattern files
• Bump Map files
• Current workspace files
• All configuration files
• All user interface files
In addition, you can create your own classes to hold additional
resource files such as plotter configuration files, tag templates,
and even non-MicroStation files.
Selecting the resources to be archived

Because the resources associated with MicroStation greatly outnumber
the actual ones used for a specific design file or set of files, the Archive
utility identifies a design file’s specific resources. This resource
identification function (called the selection component) is invoked
when you add files to a new or existing archive file. After selecting
files and adding them to the archive, an alert box opens to confirm
whether or not you want to see the classes for the selected file(s). If
you click Yes, the Select Archive Classes dialog box opens.

For the current design file, all the resources used are listed by class
(in the Select Archive Classes dialog box’s Class list box). As you
select a resource class, the specific files of that class which are
currently in use are displayed in the Item list box.
The Archive utility only archives entire files. There is no

mechanism to extract an individual font or line style from a
file and archive only that component.
By default, when a resource class is selected by clicking the option
box next to its name, all of its individual items are automatically
identified for archival and displayed in the Item list. By deselecting
the option box next to specific items in the Item list, you can
remove a specific component from the list. This is especially helpful
when transferring files from/to systems with a high degree of
common resources (a satellite office, for instance).
The archive process

Once all of the items to be archived are identified, the archive process is
started. After you type your name for the archive file (with the default
extension .mar), the Archive utility begins assembling and archiving
files. Using a widely accepted compression algorithm, the Archive
utility attempts to compress the files into a tighter format requiring
less disk storage space. In the event the compression algorithm cannot
decrease the file size, the file is stored as is in the archive file.
For those situations when you may not want to create a compressed
archive file, the Archive utility can be directed to copy the various
resource files into a directory of your own choosing.
The extraction process

Because the Archive utility creates a special archive file format, a
provision to restore the files to their original format is needed. To
this end, the Archive utility provides an Extract function. After
identifying the files you wish to restore from the archive file,
the Archive utility extracts those files from the archive file and
copies them to a directory specified by the user.
Because many of the resources are found in the standard MicroStation

directory structure, the Archive utility will alert you when it

Creating and manipulating archive files
encounters a duplicate name. You can overwrite the identified

file or skip it. In addition, there is an option on extraction that
will automatically overwrite existing files.

When you launch the Archive utility, the Archive dialog box
opens. The focus of the Archive utility’s operations, this dialog
box lists the files which constitute the currently opened archive
file, along with some information about these files.
General Procedure — To use the Archive utility
1. From the Utilities menu, choose Archive.

The Archive dialog box opens.
Archive
dialog box
2. Create a new archive file. (see page 6-101)

or
Add to an existing archive file. (see page 6-101)
or
Copy a file and its related resources to a new destination.
(see page 6-104)
or
Extract a file or files from an existing archive file. (see page 6-105)
3. Close the Archive dialog box.

To create a new archive

1. In the Archive dialog box, click the New Archive icon.
The Create Archive File dialog box opens.
2. Enter a name for the new archive and click OK.
By default the archive filename is given the .mar extension.
The name of and path to the new archive appear in the title bar
of the Archive dialog box. For example, MicroStation Archive
- C:\Bentley\Workspace\system\data\new.mar.
To open an existing archive

1. In the Archive dialog box, click the Open Archive icon.
The Open Archive File dialog box opens.
2. Select an archive file and click OK.
The files constituting the selected archive file are displayed
in the Archive dialog box’s list box.
To open a remote archive

1. From the Archive dialog box’s File menu, choose Open URL.
The Open Remote Archive dialog box opens. The controls in
this dialog box are analogous to those in the Select Remote
Design File dialog box (refer to the Reference Guide for
descriptions of the controls in this dialog box).
2. In the URL field, specify the path to the remote archive.
3. (Optional) — Adjust any other settings necessary.
4. Click OK.
To add files to an existing archive

2. Select the archive file to be updated and click OK.

3. Click the Add Files icon.

The Select Files To Add dialog box opens.
4. Select a file to add to the archive and click the Add button.
The file appears in the Files list box at the bottom of the dialog box.
5. Continue selecting files to archive. When all files to be archived
have been identified, click the Done button.
The Add Archive Files dialog box opens to allow you to make
path selections for the selected files.
6. (Optional) — Turn on Save Directories.
This stores the file path specification in the archive
file. If this option is not selected, only the file names
are stored in the archive file.
Also, turning on Save Directories enables the Use
Path Filter option.
7. (Optional) — Turn on Use Path Filter and click the Select

button in the Path Filter section.
The Select Path Filter dialog box opens. Selecting a path sets the
path filter as follows: only that portion of each file specification
that is not defined in the Select Path Filter dialog box is archived.
This option acts as a filter to remove that part of the path that
is unique to a specific system (for instance, the MicroStation
directory: “Bentley\Program\MicroStation”). Note that drive
designators are never stored as part of an archive.
8. (Optional) — Enter a relative path filter and click OK.
9. In the Add Archive Files dialog box, click OK.

An alert box opens to confirm whether or not you want to
see the classes for the selected file(s).
10. Click Yes to open the Select Archive Classes dialog box.
If you click No, the archive process begins and this
procedure is over.
11. If you clicked Yes, choose the specific archive classes you wish to
archive by selecting the check boxes alongside their names.
As a class is selected, any items specifically called for in the design
(reference files, resource files, fonts, etc.) or related to the current

MicroStation session (workspace, configuration and user interface

files) are displayed in the Item list box. By default, they are
automatically selected for archival. Click their related option box
to select or deselect each file listed for the selected class.
12. (Optional) — In the Select Archive Classes dialog box,
click the Reports button.
The Archive Report dialog box opens, which is used to review
the resource file tree used by the current design file.
In the Archive Report dialog box, you can select the style of the
report, as follows: you can view a summary of the classes (by
choosing File menu > Style > Class Summary), a tree structure
showing interdependencies (by choosing File menu > Style >
Dependency Tree), or a straight listing of the files (by selecting
File menu > Style > File List). You can also save the current
view to a text file by choosing Save from the File menu.
13. Once all of the classes have been selected, from the Method
option menu, choose Create Archive File.
14. Click OK.
The archive process begins. A progress indicator is displayed
showing the name of the file being processed, as well as the
progress of the entire archive process.
When complete, the added files are displayed in the
Archive dialog box’s list box.
To create and add files to a new archive

1. With no archive currently open, in the Archive dialog
box, click the Add Files icon.

2. Follow steps 4–14 in the procedure To add files to an

existing archive (see page 6-101) .
3. When you get to the Create Archive File dialog box, enter a
name for the new archive and click OK.
The archive process begins. A progress indicator is displayed
showing the name of the file being processed, as well as the
progress of the entire archive process.
By default the archive filename is given the .mar extension.
When complete, the contents of the archive file are
displayed in the Archive dialog box’s list box, and the
name of and path to the new archive file appear in the
dialog box’s title bar. For example, MicroStation Archive -
C:\Bentley\Workspace\system\data\new.mar.
To copy a design file and its resources to

a new destination
1. In the Archive dialog box, click the Add Files icon.
2. Follow steps 4–12 in the procedure To add files to an
existing archive (see page 6-101) .
3. In the Select Archive Classes dialog box, once all the
classes have been selected, click the Method option
button and choose Copy Files.
This instructs the Archive utility not to create an archive file, but
instead to copy the bundled files to a selected directory.
4. Click OK.
The Copy Files dialog box opens.
5. Select a directory to which to copy the selected design
files and resource files and click OK.
The Archive utility copies the selected files to the
selected directory, and provides a progress indicator and
operation complete information.

To extract files from an existing archive

2. Select the archive file from which files are to be
extracted and click OK.
The files which constitute the archive file are displayed
in the Archive dialog box’s list box.
3. In the list box, select the files to be extracted. Standard list
selection techniques can be used to select more than one file.
To select all files in an archive use the Select All item
in the Archive Edit menu.
4. Click the Extract Files icon.
The Extract Archive Files dialog box opens, displaying information
about the selected files along with destination options.
5. (Optional) — Select the Create Stored Directories option.
By default, the Archive utility will not use any directories stored as
part of the archived file’s path. By selecting this option, you direct
the Archive utility to use stored directories as the destination path.
6. (Optional) — Select the Overwrite Existing Files option.

When this option is selected, the extracted file will overwrite
an existing file with the same name.
7. (Optional) — Select the Preserve Date/Time option.

If on, the date/time of the extracted file will be copied from the
compressed file, preserving its original values.
8. (Optional) — In the Extract To section, click the Select button.

The Extract To dialog box opens.
9. (Optional) — Select a new path for the target directory to which

the selected design files will be restored and click OK.
10. In the Extract Archive Files dialog box, click OK to begin

the file extraction process.

Digital Signatures
Digital Signatures
A digital signature determines if a document is identical to
the document that was signed and shows the identity of the
signer. Signatures are stored with a compressed copy of the
file inside the archive. A document with a good signature
has the following qualities; it is:
• Authentic — The signature indicates the signer’s intention

to sign (authenticate) the document.
• Un-forgeable — The signature could not have been created
by anyone other than the signer.
• Not reusable — The signature is specific to the document. It
will not validate any other document.
• Unalterable — The document cannot be altered without
invalidating the signature.
• Repudiation — The signer cannot at a later date deny
signing the document.
A digital signature does not keep the document from being modified.
It does not lock the document, and it does not prevent others from
signing the document, either modified or unmodified.
Typical uses of digital signatures
The following are common situations involving digital signatures.
1. All the engineers that worked on a project have to sign

off on an electronic document, and they are not all able to
be in the same room at one time.
• Each engineer signs the file using his or her private

and public keys. This can be done over a network, and
can be done at separate times.
• All the signatures are gathered and all verified against the
original document. The signatures can be verified in any order.
• Once all the signatures have been verified, one document
containing all the signatures can now be delivered.
2. Engineer A wants to ensure that the file he shipped over the

Internet to engineer B is the exact file that he sent:

Digital Signatures
• Engineer A signs the file, then sends the file with the signature.
• Engineer B verifies the signature, inspects the file and adds her
signature, then sends the file back to engineer A.
• Engineer A verifies engineer B’s signature, which
verifies the original file.
General Procedure — To digitally sign files

1. Open the Archive dialog box (Utilities > Archive ) and
select an archive file.
2. If necessary, update the file (see page 6-111) .
3. If necessary, create a new key pair (see page 6-107) .
4. Sign the file (see page 6-109) .
Key pairs
The encryption tools used for digital signatures use two keys known
as key pairs (large numbers that satisfy certain mathematical
relationships). One is used to encrypt a hash of the document
(the private key), and the other is used to decrypt the signature
to verify the signature (the public key). The public key can be
freely distributed for other encryption needs.
The configuration variable MS_KEYPAIRLIST defines

where the key pair files are stored (the default directory is
"\Bentley\Workspace\users\*.kpf").
To create a key pair

1. In the Archive dialog box, click the Sign Files icon.
The Load Key Pair dialog box opens.

Digital Signatures
Load Key
Pair dialog
box
2. Click Create.
The Create Key Pair dialog box opens.
Create Key
Pair dialog
box
3. Type the appropriate information in the Key Pair Name,

Name, Organization, Email, Comment, Password, and
Verify Password text fields.
4. Click OK.
Your key pair is created and saved in the default directory.
If you select a file in the Archive dialog box’s list box before you
create the key pair, clicking OK in the Create Key Pair dialog box
signs the selected file in addition to creating the key pair.
Keeping the private key private

The private key ensures that the owner of the key is the only one who
could have created the signature. It is encrypted with the password in
the key pair file. The security of the private key ensures the document

Digital Signatures
is authentic, un-forgeable and cannot be repudiated. The encryption

and hash functions guarantee the signature is not reusable and the
file cannot be altered without invalidating the signature.
Signing Documents
Only the owner of the private key can create a signature that works
with his public key. The signature contains an encrypted hash of
the document, the name of the key pair, the public key, and the
time and date of signing. Certificates (the public key and related
text information) are also stored in the archive.
To sign a file
1. In the Archive dialog box’s list box, select the file(s) you want to sign.
If no files are selected, all files in the list box will be signed.
2. Click the Sign Files icon.
The Load Key Pair dialog box opens.
3. Select a key pair from the Key Pair Name List list box.
or
Click Browse to open the Find Key Pair file dialog box.
Select a key pair and click OK.
4. In the Load Key Pair dialog box, type the password for the
selected key pair in the Password text field.
5. Click OK.
The file is signed and the Signing and Verification
Results text window displays.

Digital Signatures
Verifying Documents
Anyone can verify a signature by using the public key that is in the
signature. All you need is a file to verify and a signature for that file.
The encrypted hash from the signature is decrypted using the public
key from the signature. A second hash is obtained by hashing the file.
If the two hashes are equal, then the signature is valid.
The signature is either valid or invalid if the file is or is not

identical to that which was signed. The identity of the signer
and the time and date of the signature are also reported in the
Signing and Verification Results text window.
Verifying does not alter the archived file(s).
To verify a file
1. In the Archive dialog box’s list box, select the file(s)
you want to verify.
If no files are selected, all files in the list box will be verified.
2. Click the Verify Files icon.
The Signing and Verification Results text window displays.
Updating files
If you want to digitally sign a file that was archived with an

earlier version of the Archive utility, you have to update it to
allow for digital signature information.

Digital Signatures
To update an archived file

1. From the Archive dialog box’s File menu, choose Open.
The Open Archive File dialog box displays.
2. Select a file that was archived with an earlier version of
the Archive utility, and click OK.
A prompt displays, asking if you want to update the file.
3. Click Yes.
The file is updated to the new archive format and added to the
Archive dialog box. You can now sign the file (see page 6-109) .
Alternative method — To update an archived file

1. If you opened the file without initially updating it, from
the File menu, choose Save As….
The Save Archive File As dialog box opens.
Save Archive
File As dialog
box

Other aspects of the Archive utility
2. Turn on the Retain all Signature Information (new

format) radio button.
3. Select a file and click OK.
The file is updated to the new archive format and added to the
Archive dialog box. You can now sign the file (see page 6-109) .
Algorithms used for digital signatures

The following describes algorithms and other requirements
for digital signatures.
• Hash function: SHA1. Input: a file of any size.

Output: a 160-bit value.
• Signing algorithm: DSA. Uses a 160-bit private key
and a 512-bit public key.

The Archive utility also provides a number of functions not easily
categorized. The following are short descriptions of these functions.
Working with Windows Explorer

The Archive utility also provides the ability to interact with
Windows Explorer or its equivalent. For example:
• If the Archive dialog box is open but empty and you drag
non-archived files from Windows Explorer into the dialog box,
the Archive utility interprets this as a command to create
an archive file. After adding the file(s) and selecting the
files’ archive classes in the appropriate dialog boxes, you are
prompted to name the archive file. Once archived, the files
are listed in the Archive dialog box’s list box and the name
of the archive file appears in the title bar.
• If the Archive dialog box is open but not empty and you
drag non-archived files from Windows Explorer into the
dialog box, the Archive utility behaves the same as in the

scenario above, with the exception of not requesting a name

for the archive since it already exists.
• If the Archive dialog box is open, empty or not, and you drag
an archived file (having default file extension .mar) from
Windows Explorer into the dialog box, the title bar changes to
the name of that archive file, and information about the files
constituting that archive file is displayed in the list box.
Working with your own resource classes

When you create an archive, the ability to identify classes of resources
is very helpful, especially when your project includes many different
files. In addition to all of the files associated with MicroStation, many
projects utilize other files that are either not part of MicroStation or
are not considered a class by the Archive utility. In these cases, you can
create your own archive classes and include them in your new archive.
The Archive utility provides a facility to create and use custom

resource class definitions. This is available in the Select
Archive Classes dialog box, which is optionally the last dialog
box you see before the file is archived.
To create a user defined class file

1. From the Select Archive Classes dialog box’s UserClass
menu, choose New….
The Create Archive Class dialog box opens.
2. Click the Create button in the Class File section of this dialog box.
The Archive Class File dialog box opens. Enter the name and
path of your new class file. By default, the Archive utility uses
the environment variable "MS_ARCHIVECLASS" to locate
these files. The .mac file extension is used by default.
The selected file name is displayed in the Create Archive
Class dialog box, above the Create button.
4. In the Create Archive Class dialog box, key into the
Description field. This is important, as the description
is used in subsequent operations.

5. Click the Files button.

The Archive Class Files dialog box opens.
6. Select a file name you wish associated with the current class.
The selected file appears in the Files list box at the
bottom of the dialog box.
8. Repeat steps 6 and 7 until all of the files you want to appear in
your new class are identified (displayed in the Files list box), then
click Done to return to the Create Archive Class dialog box.
9. Click OK to return to the Select Archive Classes dialog box.
The user-defined class appears in a highlight color at the bottom
in the list of standard classes. Selecting this class displays
the list of files bundled into this class (steps 6-7).
To use an existing user class file

1. When the Select Archive Classes dialog box first opens, only the
predefined classes are listed. User-defined classes, if desired,
must be added each time the dialog box is opened.
2. From the Select Archive Classes dialog box’s UserClass
menu, choose Add.
The User Defined Classes dialog box opens and lists
all user-defined classes.
3. Select a user class and click OK.
The selected user-defined class appears in a highlight color
at the bottom in the list of standard classes. Selecting this
class displays the list of files bundled into this class.

Part III: Internet Technologies
Engineering Links
Designed to embrace the new engineering workflow, Engineering
Links is a series of Web-enabling technologies that simplifies
management of your MicroStation-based engineering projects.
Engineering Links forms a solid foundation for tomorrow’s completely
collaborative MicroStation engineering environments.
Engineering Links tool box

The Engineering Links tool box contains tools for linking
to and managing remote data.
The Engineering Links tool box opens in the following situations:
• when Engineering Links is chosen from the Tools menu

• when MicroStation Links is chosen from the Utilities menu
• when SELECTservices is chosen from the Help menu
• when the SELECTservices icon is selected in the Standard tool box.
All but the first option listed here also launches your
default Web browser.

Engineering Links
Show Engineering Links
To Select in the
Engineering Links
tool box
Highlight all the elements in the design
file that contain an Internet tag.
Show Engineering
Links (see page 7-2)
Create an Internet tag and attach
it to an element.
Attach Engineering
Link (see page 7-3)
Send the browser to the Web page
specified by the Internet tag attached
to an element.
Following Engineering
Link (see page 7-5)
ConnectMicroStation to or disconnect it
from your default Web browser.
Connect to/Disconnect
from Browser (see
page 7-5)
Maintain local copies of remote
reference files.
Load RefAgent (see

page 7-6)
Key-in: DIALOG WEBTOOLS
Show Engineering Links

Used to highlight all the elements in the design file that
contain an Internet tag.

Engineering Links
Attach Engineering Link
To show all elements containing Internet tags

1. Select the Show Engineering Links tool.
The line style and color of elements in the design file containing
an Internet tag changes to dashed and blue.
2. Select the Show Engineering Links tool again to return elements
containing Internet tags to their normal display.
Key-in: SHOW WEBTAGS áOFF | ON | TOGGLEñ

Used to attach an Internet tag to an element. After attaching
an Internet tag, selecting the tagged element using the Follow
Engineering Link (see page 7-5) takes you to the Internet
address specified in the tag.
Tool Effect
Setting
Link Sets the type of link you are creating: HTML or XML.
Type If you are creating a simple XML link, you can specify
parameters which further define how the link should
operate (See the Role and Show descriptions below).
URL The Internet address to which to link the element.
Title The logical name of the Internet address
in the URL field.

Engineering Links
Tool Effect
Setting
Role (Enabled when Link Type is Xlink:simple) Specifies
what role the object of the link will specify, for
example, that of a reference file or cell library.
Show (Enabled when Link Type is Xlink:simple)
Determines whether any existing page should be
replaced or if a new browser should be opened.
To attach an Internet tag to an element

1. Select the Connect to Browser tool.
If your default Web browser was not open, it opens now,
and MicroStation connects to it.
2. In the Web browser, navigate to the exact Internet address
to which to link the element.
For example, http://www.bentley.com/products/index.htm.
3. In MicroStation, select the Attach Engineering Link tool.
The Attach Engineering Link dialog box opens with the URL
field automatically pointing to the Internet address open in your
Web browser. If you want to change this address, go back to the
Web browser, navigate to a new location, and select the Attach
Engineering Link tool again to refresh the address in the URL field.

Engineering Links
Follow Engineering Link
4. (Optional) — Change any of the fields or settings necessary.
5. Identify an element and accept to attach the tag.
Key-in: ATTACH WEBTAG
Follow Engineering Link

Used to send the browser to the URL specified in the selected
element’s attached Internet tag.
To “jump” to the URL specified in an

element’s Internet tag
1. (Optional) — If you are not sure which elements contain Internet
tags, select the Show Engineering Links tool.
2. Select the Follow Engineering Link tool.

3. Identify the element containing the desired Internet tag
and enter a data point to accept.
If it is not already open, the Web browser opens and takes
you to the URL specified in the Internet tag.
Key-in: FOLLOW WEBTAG
Connect to/Disconnect from Browser

Used to connect MicroStation to or disconnect it from
your default Web browser.

Engineering Links
Load RefAgent
To connect MicroStation to the default

Web browser
1. Select the Connect to Browser tool.
The default Web browser opens, if not open already, and
MicroStation connects to it.
To disconnect MicroStation from the

default Web browser
1. Select the same tool, whose icon has slightly changed and whose
tool tip now says Disconnect from Browser.
If you had originally opened the browser through one of the
Engineering Links tools or by choosing MicroStation Link,
selecting Disconnect from Browser closes the browser in addition
to disconnecting it from MicroStation. If you had opened the
browser from outside MicroStation and then connected to it,
selecting Disconnect from Browser only disconnects MicroStation
from the browser without closing the browser.
Key-in: BROWSER CONNECT
Load RefAgent
Opens the Reference File Agent dialog box, which is used to
maintain local copies of remote reference files.
For information about the controls on this dialog box, see

the on-line Reference Guide.

Engineering Links
Remote Open/Attach
Reference File
Agent dialog
box
Key-in: BROWSER REFAGENT
Remote Open/Attach
The Remote Open/Attach function allows you to select a URL as a
design file location instead of a specific local design file. URLs can
also be attached to a remote settings file, archive, reference file, or
cell library. Downloaded files from a URL are stored in a directory
specified by the configuration variable MS_WEBFILES.
The dialog box for creating a URL (for example, the Select Remote
Design File dialog box) has the same appearance no matter which
type of file is being attached. The methods for creating each type
of URL are described in the following procedures:
• To open a remote design file (see the “Fundamentals” chapter

in the MicroStation User’s Guide)
• To open a remote settings file (see the “Placing Elements in

2D” chapter in the MicroStation User’s Guide)
• To open a remote archive (see page 6-101)
• To attach a remote cell library (see the “Using Cells” chapter

in the MicroStation User’s Guide)
• To attach a remote reference file (see the “Reference Files”

chapter in the MicroStation User’s Guide)

Engineering Links
Entering the URL
Entering the URL

Once you have reached the dialog box for creating the URL you can
enter the URL into the address field by using one of following methods:
• Selecting a bookmark
• Choosing an entry from the history
• Typing in the desired location
Bookmarks are stored in one of several files, depending on the data
type. Current types and the associated configuration variables are:
Design Files MS_BOOKMARKS_DGN

Cell Libraries MS_BOOKMARKS_CELL
Archives MS_BOOKMARKS_ARCHIVE
Resources MS_BOOKMARKS_RSC
Images MS_BOOKMARKS_IMAGE

Publishing Data to the
Internet
This section provides information on MicroStation features
that help you publish data to the Internet.
Using HTML Author

HTML Author is used to create HTML files that can be viewed
via any Web browser. HTML files can be created from a
Cell Library, Design File Saved View, MicroStation BASIC
Macros, or a Design File Snapshot.
To open the HTML Author dialog box

1. From the Utilities menu, choose HTML Author….
The HTML Author dialog box opens.
To create an HTML file from a Cell Library

1. In the HTML Author dialog box, select Cell Library.
2. Click OK.
The Select Cell Library to Open dialog box opens.
3. Select a cell library file and click OK.
The HTML Cell Page dialog box opens.

Publishing Data to the Internet
Using HTML Author
4. Adjust any settings necessary and click OK.

The Create HTML File dialog box opens.
The HTML file is created and stored in the directory defined in
the Create HTML File dialog box’s File Name field. If Display
File In Browser is checked, clicking OK also opens your default
Web browser to display the newly created HTML file.
To create an HTML file from a saved

view of a design file
1. In the HTML Author dialog box, select Design File Saved Views.
2. Click OK.
The Select Design File dialog box opens.
3. Select the file containing the desired saved view and click OK.
The Design File Walkthrough dialog box opens.

Using HTML Author

To create an HTML file from a directory of

MicroStation BASIC macros
1. In the HTML Author dialog box, select Basic Macros.
2. Click OK.
The Select Basic Macro Directory dialog box opens.
3. Navigate to the desired directory and click OK.
The Basic Macro HTML Page dialog box opens.

Using HTML Author

To create an HTML file of a design file snapshot

1. In the HTML Author dialog box, select Design File Snapshot.
2. Click OK.
The Select Design File dialog box opens.
3. Select a design file and click OK.

Using HTML Author


Using HTML Author

Part IV: Using Software Extensions
Scripts, Macros, and User
Commands
To more efficiently perform specific tasks with MicroStation,
you can use specialized application software. These kinds of
application software are available:
Key-in Scripts (see page 9-1)

Macros (see page 9-1)
User Commands (see page 9-3)
Key-in Scripts
The simplest software applications are key-in scripts. A key-in
script is a sequence of MicroStation key-ins that is stored in
a text file. For example, the following script sets the Active
Level, Active Color, and Active Line Weight:
active level 24
active color blue
active weight 2
To load and run a key-in script

1. In the Key-in window, key in @<script_file>
SCRIPT_FILE must include the full path to the script if the
script is not in the current directory.
Macros
Macros are BASIC programs that automate often-used, usually
short sequences of operations. Many MicroStation-specific
extensions have been added to the BASIC language to customize
it for the MicroStation environment.

Scripts, Macros, and User Commands
Running macros
In its simplest form, a macro “drives” MicroStation in much the

same way a human user does. Macros select tools and view controls,
send key-ins, manipulate dialog boxes, modify elements, and more,
using many of the tools documented in this guide. The obvious
advantage of writing a macro to perform a task that could otherwise
be done manually is automating mechanical and repetitive tasks.
Several sample macros are supplied with MicroStation.
Macro code is stored in text files. The macro language is BASIC

with MicroStation-specific extensions. Compiled macros are
stored in resource files with .ba extensions.
Several sample macros are supplied with MicroStation. For

information about developing your own macros, see “Introduction to
Macros” and the chapters that follow in the MicroStation BASIC Guide.
Running macros
You can load, run and edit a macro using the Macros
dialog box or a key-in.
To load and run a macro

1. From the Utilities menu, choose Macros.
The Macros dialog box opens.
Macros
dialog box

User Commands
2. In the Macro Name list box, select the macro.

3. Click the Run button.
Alternative method — To load and run a macro

1. From the Utilities menu, choose Macros.
The Macros dialog box opens.
2. Click the Browse button.
The Select Macro dialog box opens.
3. Key in or select the desired macro, and click the OK button.
The Start Macro dialog box opens.
4. Click the Run button.
Alternative method — To load and run a macro

1. In the Key-in window, key in: MACRO <macro_name>
[arg1 arg2 …argn]
You can define an action string that specifies a key-in that runs a
macro and assign the action string to a custom tool, menu item,
function key, or AccuDraw keyboard shortcut. In this way, you
can run frequently used macros with a single click or key press.
See Customizing the User Interface on page 4-1.
User Commands
User commands (UCMs) are programs that follow the logic and
syntax of the UCM language. Sample UCMs are installed in
Bentley’s “Workspace\system\ucm” directory.

Indexed UCMs
To activate a UCM
1. In the Key-in window, key in USERCOMMAND <ucm>
or
UC= <ucm>
UCM is the UCM file. If the extension is omitted,
“.ucm” is assumed.
Alternative method — To activate a UCM

1. From the Utilities menu, choose User Command > Run….
The Run User Command dialog box opens.
2. In the list box, select the UCM.
With either method, MicroStation searches for the UCM:
1 . In the directory pointed to by the MS_UCM configuration variable
2 . In the current directory.
Indexed UCMs
A user command (UCM) index file is a text file that contains an
indexed list of up to 999 UCMs. Indexed UCMs can be activated by
index number as well as by name. UCM index files can be created and
edited with the Edit User Command Index File dialog box.
Before you can use an indexed list, you must activate the
UCM index file containing the list.
If a UCM index file is active, it is automatically deactivated

when the design file is closed.

Indexed UCMs
To activate a UCM index file

1. In the Key in window, key in: ACTIVE INDEX <filename>
or
Key in OX=<filename>
If you do not specify the full path, MicroStation searches in the
directory pointed to by the MS_DATA configuration variable.
If the file extension is omitted, “.ndx” is assumed.
To activate an indexed UCM

1. In the Key in window, key in: UCI <index_number>.
General Procedure — To edit UCM index files
1. From the Utilities menu, choose User Command >

Edit UCM Index File.
The Edit User Command Index File dialog box opens.
Edit User
Command
Index File
dialog box
2. In the Edit User Command Index File dialog box,

choose File > Open.
The Open UCM Index File dialog box opens.

Indexed UCMs
3. Select a file in the list box and click OK. The UCM index
file is not automatically active.
4. Click the Append button to add an entry for each
UCM to index to the list.
5. Save the list in a UCM index file:
To make a new file, in the Edit User Command Index
File dialog box, choose File > Save As. Then specify the
new name and destination of the UCM index file in the
Save UCM Index File dialog box.
To overwrite an existing file, click Save in the Edit User
Command Index File dialog box.
If you save the list to a different UCM index file, that file
is opened for editing. However, UCMs in the list cannot be
activated by index number until the file is activated with
the ACTIVE INDEX (OX=) key-in.
If a UCM index file is active, the name of the file is displayed

in the dialog box and the indexed list is displayed for editing
in the User Command list box.
UCMs with updated index numbers (including UCMs new to the

list) cannot be activated by their new index numbers until you save
the list to the original UCM index file or a different one.
To edit the name of a UCM in the list

1. Select the entry for the UCM in the User Command list box.
The name of the UCM is displayed for editing in the
text field above the list box.
2. In the text field, edit the UCM name, and press áReturnñ.
To insert a new blank entry in the list

1. Select the entry before which you want to insert the new entry.
The index number of each entry after the new entry is incremented.

Indexed UCMs
To delete an entry
1. Select the entry.
The index number of each entry that was after the
deleted entry is reduced.

Indexed UCMs

MDL Applications
MDL applications are extensions to MicroStation. MDL stands
for MicroStation Development Language — essentially the C
language executed by MicroStation. Many parts of standard
MicroStation are actually MDL applications.
Bentley Enterprise Developer Program members around the world

offer products and services that compliment Bentley engineering
solutions. The Enterprise Developer’s catalog, located on Bentley’s
developer Web site (http://www.bentley.com/developer/catalog.htm),
describes hundreds of commercially available MDL applications. The
catalog has search capabilities to locate products and services by
company name, product name, or application area.
An MDL application can only be used in MicroStation. MicroStation

can be (and almost always is) operated with more than one MDL
application loaded at a time. MicroStation can manage multiple MDL
applications simultaneously. In fact, there are no practical limitations
placed on the number of MDL applications that can be loaded.
Some MDL applications insert their own sub-menus in the

Applications menu in MicroStation’s main menu bar. (The
Applications menu only appears in the menu bar when an MDL
application has inserted a sub-menu in it.)
In this chapter, you will find procedures concerning MDL

applications, including:
• Loading and Unloading MDL Applications (see page 10-2)
• Loading MDL Applications Automatically (see page 10-4)
For information about designing and programming MDL

applications, see “MicroStation Development Environment”
in the MicroStation BASIC Guide.

MDL Applications
Loading and Unloading MDL Applications

The MDL dialog box (Utilities > MDL Applications) can be used
to load and unload MDL applications.
To load an MDL application

1. From the Utilities menu, choose MDL Applications.
The MDL dialog box opens.
MDL dialog
box
2. In the Available Applications list box, select the application.

3. Click Load.
Alternative method — To load an MDL application

2. Click the Browse button.
The Select MDL Application dialog box opens.
3. Key in or select the desired MDL application, and
click the OK button.

MDL Applications
Alternative method — To load an MDL application

1. Key in MDL LOAD <application_name>.
For example, to load the MDL application MERGE (merge.ma),
key in MDL LOAD MERGE.
MDL applications that are part of standard MicroStation are not listed
in the Available Applications list box in the MDL dialog box. However,
upon loading, they are listed in the Loaded Applications list box.
To view technical details about an MDL

application
2. In the Loaded Applications list box, select the desired application.
3. Click the Detail button.
To view key-ins for an MDL application

2. In the Loaded Applications list box, select the desired application.
3. Click the Key-ins button.
The Key-in window opens, displaying the key-ins that are
associated to the selected MDL application.
To unload an MDL application

2. In the Loaded Applications list box, select the application.
3. Click the Unload button.

MDL Applications
Loading MDL Applications Automatically
Alternative method — To unload an

MDL application
1. Key in MDL UNLOAD <application_name>.

You can have selected MDL applications load automatically
every time you open a design file.
To specify MDL applications for automatic loading

2. In the Category list box, select Design Applications.
The controls for selecting applications for automatic loading
are shown to the right in the dialog box.
Configuration
Variables
dialog box
3. In the Available Applications list box, select an MDL application

that you want to load automatically upon start-up.

MDL Applications

The application’s name is shown in the Applications
to Load list box.
5. Repeat steps 3 and 4 until all the desired applications’ names
appear in the Applications to Load list box.
6. Click OK.
MDL applications that require more control over MicroStation

are referred to as “initapps” after the name of the configuration
variable (MS_INITAPPS) that specifies them. Using the Design
Applications configuration variable is the preferred way to
load MDL applications automatically.
For more information about modifying configuration variables, see

Working With Configuration Variables on page 3-7.

MDL Applications

Part V: External Database Interface
MicroStation and
Non-graphical Data
Typically private enterprise and government entities manage two
significant data sets about their physical plant or products:
• Architectural or engineering design drawings
• Non-graphical data stored in organization-wide databases
One data set is typically of limited use without the other, yet many
times the sets are kept separate. The non-graphical data is printed
and added to drawings only after they are plotted. While this approach
may be fine for a production shop, it may be inappropriate for a project
manager who wants intelligent, useful drawings for the life of a project.
Several advanced design applications link non-graphical

data to drawings — for example, products such as Facility
Management Systems and Geographic Information Systems
(GIS) do this very well. The one aspect most of these systems
have in common is that the database interface is built into the
application and is hidden from the user.
Associating Elements to Non-graphical Data

MicroStation lets you build your own application that associates
non-graphical data to graphical elements, including text and cells, using
standard interfaces that are part of MicroStation. This association
can be accomplished using either of two MicroStation features:
• Element tags, where associated data is stored in the design file
with the graphical elements. Tags are appropriate if your needs
for associating non-graphical data to elements in the design file
are relatively simple or you must maintain compatibility with
other CAD packages that store data inside their drawing files.
The associated tag data may be copied from the tag, loaded into
a database and liked back to the tag. For more information,
see Tagging Elements in the User’s Guide.

MicroStation and Non-graphical Data
Tag to Database Converter
• Database interface, where associated data is stored in a separate

relational database that is linked to elements in the design file.
The remainder of this chapter covers the database interface.
Tag to Database Converter

The tag to database converter exports tag data from the design file
into an existing database table for use with MicroStation’s database
interface. When exporting the tag data, the application scans the
design file for elements which have tag data attached, extracts the
tag data, and builds and executes an Insert statement to add the tag
data to a database table. The application adds a database link to
the element for the row which was inserted into the table.
For general information about tag data, see Tagging

Elements in the User’s Guide.
What is the Database Interface?

The database interface is a set of tools and settings that lets you
associate (or link) a row in a relational database to an element in
the design. This is done by storing information about the linkage
in the element in the design file. In order to link a table to a
graphical element, the table must have a numeric MSLINK column.
This column acts as a unique row identifier (essentially a row ID)
for MicroStation. The second requirement is that the database
contains a table called MSCATALOG. The attribute table name
is entered and assigned a unique entity number.
There are two pieces of information that are used to retrieve the
correct row from the correct table. The first is the entity number,
a unique value assigned to the table in the MSCATALOG. The
second is the MSLINK number, a unique value assigned to the row

Why Use the Database Interface?
of data in the table. When a database row is linked to a graphical

element, attribute data is written to the element.
Once this linkage is established you can manipulate and review

the database information from inside MicroStation.
The following commercial database products are directly supported:

Oracle, Sybase, and Intergraph’s Relational Interface System (RIS)
and Open Database Connectivity Standard (ODBC).
RIS and ODBC are not relational databases; they are generic
interfaces that allow advanced design applications to access
SQL compliant databases.
Why Use the Database Interface?

Using the database interface offers many capabilities not otherwise
available to the CAD user. These range from a simple application
that tracks part numbers in an assembly to a sophisticated facility
management system, which tracks the operation and maintenance
of a large organization, and everything in between.
For example, a graphical element representing a street on a

map can be linked to a road or street name, traffic flow rate,
accident rate, construction date, and resurfacing data in a
database table. The centroid point and text for the lot number
of each parcel of land could be linked to another database table
that includes owner, area, and street name.
By relating the two tables, you could, for example:
• Selectively display all properties that have a value of over 100,000

dollars and a traffic flow of over 100,000 vehicles per year, and
produce a report that included each owners name and address.
• Selectively display or highlight all roads in the northeast

quadrant of the county that have a traffic flow of 50,000
vehicles a day and over 10 accidents per year.

What is a Relational Database?
• Produce a map of a subdivision showing all owners names

and property values. When the database changes you
can globally update the map.
Using the database interface requires more memory than

MicroStation’s standard memory requirements. Additional memory
improves the performance of both MicroStation and the database.
What is a Relational Database?

A relational database is an ordered collection of tables or
files that represent objects, their properties, and relationships
between the objects.
These terms are used throughout this guide:
• A relational database contains a collection of tables.
• Each table is composed of rows and columns.
Usually the tables in a database have a common column or field that

relates one to the other. Hence the term relational database.
Why Use a Relational Database?

There are many reasons to use external relational databases to
link textual information to graphics. Relational databases are by
far the most popular database models on the market today. They
are designed to hold large amounts of data. They typically use
Structured Query Language (SQL) for accessing and modifying data.
Products like Oracle and SYBASE, along with the standard SQL
model, have revolutionized how information is managed.
Microsoft’s Open Database Connectivity (ODBC) interface allows

applications, through database drivers, access to data in a variety of
database management systems (DBMS). This enables users to evaluate
their own database environment and add ODBC database drivers
without the need for changes to the ODBC-enabled application.

Database Server
Database Server
The MicroStation database interface software program for a particular
database package — for example, Oracle — is sometimes called the
database server. The server model defines the interaction between
MicroStation, the database package, and the database server.
Unless you are developing database applications for MicroStation,
you need not be familiar with the details of the server model. It is
sufficient to be aware that in the server model, database functions
are separated from graphics functions. This means:
• Different databases can be used by “plugging in” different servers.
• Database servers are developed and maintained separately

from MicroStation.
• Memory requirements for MicroStation sessions are reduced when

a database is not connected (a server is not loaded).
Choosing a Database
MicroStation supports many of the popular relational database
software product families on the market today. Selecting the “right
one” can be difficult as these databases represent a broad range in
sophistication, performance and cost. You can implement anything
from a simple single-user database on a PC to a full featured
corporate network system with database servers and different vendor
databases all interacting with the same design files.
MicroStation database interface availability varies from operating

system to operating system as follows:
• Oracle — Windows 95, Windows 98, Windows NT

(direct connection or ODBC)
• INFORMIX — Windows (via ODBC)
• Sybase — Windows NT (direct connection or ODBC)
• RIS — Windows NT
• ODBC — Windows 95, Windows 98, Windows NT — Oracle,
Informix, Xbase, SQL Server, Access, Sybase.

Selection Factors
This chapter identifies issues you should consider in selecting

a database as well as the major features of the various
supported database products.
For information on database versions supported, see Technical

Documentation on the Bentley website.
Selection Factors
There are many factors that influence the selection of a database. For
example, if only one person will use the database information you
might choose to keep it on the user’s system. Or, if several people need
access to the data you may choose to place it on a network server.
Any of the supported database products will run from a network

server, but they operate quite differently. On the single user
system, the server just stores the database file. All processing is
accomplished on the user’s system. This can result in considerable
data being passed across the network.
Oracle, Sybase, and RIS are all client server databases. Here the
database engine runs on the server. It receives requests from
client software on each user’s system. A request is processed and
only the answer is passed back across the network. This type
of database can support more users because there is less traffic
on the network. These products can also run with the client and
server software both on the user’s system.
Here are some selection criteria you should consider:
• Will the database be local or on a network server?
• Will you access the data from different types of systems (for
example, a mix of workstations running Windows NT)?
• Will you be required to run the database independent

of MicroStation?

Database Product Families
• Should the MicroStation application be independent of the

database? That is, should the application run unchanged
with different vendor databases?
• Will tabular reporting of non-graphical data be required?
• Will corporate database standards influence your selection?
• Will you have need to interface the corporate database?
• Will you be required to access more than one vendors’ database?
Database Product Families

Typically database products are not just one program or application, but
a family or suite of application tools to allow you to build, maintain, and
report your information. Because MicroStation supports such a broad
range of commercial databases you should familiarize yourself with the
capabilities of each family of products before you make a selection.
Oracle
Oracle, by Oracle Corporation, is a very popular database
based on the client-server model.
Oracle offers several database products with varying capabilities

that can be used with MicroStation. Although there are significant
differences between these products, the MicroStation issues
revolve around the following questions:
• Is access required to a local or remote (on a server) database?

• Will access be required from several different types of systems?
The following table lists Oracle products and requirements for
their use with local and remote (on a server) databases:

Oracle
Product Local Database Remote

Database
RDBMS Required (not applicable)
SQL*Report Optional Optional
Writer
SQL*Forms Optional Optional
SQL*Plus Required Optional
SQL*Net Optional* Required
Required Support Required Required
Files
* Required to support remote clients
Product descriptions
These Oracle products are of interest to the MicroStation user:
Product Description
Oracle (base The core of the relational database
product) management system. It includes
features that control data storage,
retrieval, and security.
Oracle
development
tools
Oracle Tools for developing and running
SQL*Forms forms-oriented applications with Oracle.
Oracle A non-procedural application
SQL*Re- development tool advanced report
portWriter generation with pop-up menus and
powerful formatting capabilities.
Oracle A fourth-generation menu development
SQL*Menu tool that provides a common front end to
both Oracle and non-Oracle applications.
Oracle Pro*C Lets developers embed database
manipulation statements into
their applications.

Sybase database
Product Description
Oracle Lets database tables from other sources
SQL*Loader be loaded into Oracle. This tool, used
in conjunction with Oracle’s DB3PREP,
makes it very easy to convert dBASE
III Plus database files to Oracle format.
These tools make it practical to use Xbase
as a prototype development platform for
more complex Oracle applications.
Oracle
database tools
Oracle Provides an interactive interface to
SQL*Plus Oracle with facilities for ad hoc queries
and database manipulations.
Oracle
Network tools
SQL*Net Lets MicroStation access remote Oracle
databases over a network.
Oracle Client
Software
Required MicroStation database server interacts
Support Files with these files to connect to a
remote server.
Sybase database
Sybase, by Sybase, Inc., is based on the client-server model as well.
If accessing a Sybase database locally, the only Sybase product

that is needed is Sybase System X or Sybase System XI. If access
to a remote Sybase database server is required, then Sybase
Open Client must be installed on the client machine. There is
no need for a Sybase forms product to be installed for use with
MicroStation, since MicroStation uses the Xbase-like forms interface
when working with Sybase. This means forms are defined in
.FMT files, using “get” and “say” statements.

ODBC Database Interface
The following table lists Sybase products and requirements for

their use with local and remote (on a server) databases:
Product Local Database Remote

Database
System X or XI Required N/A
Open Client Optional Required
The following Sybase products are of interest to the MicroStation user:
Product Description
System X or XI Core relational database engine
Open Client Client software for accessing Sybase
SQL Server System X or XI
ISQL Interactive interface for submitting SQL
statements to Sybase SQL Server
ODBC Database Interface

Microsoft’s Open Database Connectivity (ODBC) interface allows
applications, through database drivers, access to data in a variety of
database management systems (DBMS). This enables users to evaluate
their own database environment and add ODBC database drivers
without the need for changes to the ODBC-enabled application.
To use the ODBC interface, you need the following:
• Microsoft ODBC driver manager version 3.510.3002.13

or greater (32 bit)
• Windows NT 4.0, Windows 95, Windows 98
• Intersolv Data Direct NT for the following databases:
dBase IV (ver 3.01)
Oracle 8 (ver 3.01)
Sybase System 10 or 11 (ver 3.01)
SQLServer 6.5 (ver 3.01)
Informix (ver 3.01)
• Microsoft ODBC drivers for the following databases:
dBase IV (ver 3.51.1713)

RIS
Oracle 8 (ver 8.00.04.xx)

SQLServer 6.5 (ver 3.60.0319)
Microsoft Access (ver 3.51.1713)
Microsoft FoxPro (ver 3.512.1713)
The Microsoft Access ODBC driver delivered with Office97

(version 3.50.xxxx), will not work with MicroStation. You must
have version 3.51.xxxx or higher. The drivers delivered with
Office97 will cause unpredictable results.
This product does not include ODBC drivers for the supported
databases. The user must purchase Intersolv ODBC driver(s) for the
MicroStation ODBC server to function correctly, or you may download
Microsoft drivers from the Microsoft link on the ODBC technote
available on Bentley’s website. This release is only supported for
configurations that follow the above requirements. No databases other
than those listed above have been certified for this release.
For information on database versions supported, see Bentley’s website.
RIS
RIS (Relational Interface System) is an Intergraph product. It allows
an application to access a number of different database engines
(including Oracle, INFORMIX) through a common interface. The
application communicates with RIS, and RIS provides the necessary
translation to the protocol understood by the underlying database
engine. This allows applications written for RIS to switch between
different commercial databases without modifying their source code.
The RIS user interface is independent of the connected database.
The RIS interface basically consists of three parts: An application (the

MicroStation RIS interface software), a client, and a data server. The
application is supplied with MicroStation. The RIS client and data
server are obtained separately from Intergraph. The client typically
runs on the same system as the application. The data server runs on
the system on which the database engine is running. This could be the
same system on which the client software and application are running,
or it could be a remote host located somewhere on a network.

RIS
RIS tools
RIS has a complete set of tools to create and manage databases,
formulate queries, and generate reports.
Product Description
RIS Client needed to run RIS-based applications
and Runtime
Package
RIS needed only by developers creating
Development RIS-based applications.
Platform
RIS Utilities for performing tasks such as schema
(optional) management, ad hoc queries, and
bulk loading of data.
RIS Report allows for writing reports and editing
Writer relational databases. It automates,
standardizes, and simplifies network
reporting. Built on I/FORMS,
Intergraph’s standard graphics
interface, RIS Report Writer lets you
pick functions and values from a menu
to generate SQL commands. Any
non-programmer can quickly learn to
write reports and edit databases.

Connecting to Databases
This chapter discusses how to set up databases and connect
to them from within MicroStation.
Setting Up the Database Interface

Setting up MicroStation for the database has been simplified
by the delivery of database configuration files. These files are
automatically loaded when Settings > Database > Connect is chosen.
Also, the variables may be loaded automatically with the use of the
-wd<config file> switch when executing MicroStation.
Connecting to ODBC
ODBC uses a data source to maintain the connection information
for a database. MicroStation uses an ODBC data source name
for the connection string. The ODBC driver(s) must be loaded
before data sources can be created. Once the drivers are loaded, an
ODBC icon appears in the Windows Control Panel.
To set up the ODBC interface

1. Open the ODBC driver manager by double-clicking on
the ODBC control panel icon.
3. Select the ODBC driver for the DBMS that contains your data.
The data source dialog box opens.

Connecting to ODBC
4. Define the data source name (this is the string you will use
in MicroStation’s Connect to Database dialog box).
5. (Optional) — Provide a description.
For the remaining settings, look at the table below for
your specific database. Refer to your ODBC driver manual
for specifics on other fields.
Database Action
Access Click the Select button to pick the *.mdb file.
The delivered Access example database is
“c:\Bentley\Program\MicroStation\database\
odbc\examples\access\gis.mdb”.
Xbase Provide the database directory (the directory
that contains the .dbf and index files.
“Locking” is the level of locking on a dbf
file. The locking field should be set to “File”.
This will ensure that, with multiple users,
active entities will not collide. If your index
files are the same name as your dbf files,
you do not have to click the Define button to
associate the index file to the dbf.
The delivered Dbase IV gis example is
“c:\Bentley\Program\MicroStation\database\
odbc\examples\db4\”. The
delivered FoxPro gis example is
“c:\Bentley\program\MicroStation\database\
odbc\examples\foxpro\”.

Connecting to ODBC
Database Action
Oracle Provide the server name, then from the
Advanced tab, the default user name.
‘Server Name’ is the Oracle remote
connection string. If you are connecting
remotely to an Oracle server, enter the
Oracle remote connection string, i.e.,
<username>/<password>@database_alias.
Database alias is the alias created in the Oracle
SQL Net or Net 8 Easy Configuration utility.
If the database is local, leave this field blank.
The DSN (Data Source Name) must be
defined in the ODBC Data Source. The
Server and User ID can also be defined
in the ODBC Data Source; the password
cannot. The password can however be set
as an MS_ODBCPARAMS variable.
Sybase Provide the server name and database
name on the General tab. Provide the
default login name on the Connection tab.
Sybase is case sensitive.
“Server Name” is the server name listed
in the sql.ini file.
To connect to an ODBC database from

within MicroStation
1. From the Settings menu, choose Database > Connect.
The Connect to Database dialog box opens.
2. Set the Database Server to ODBC.
3. Provide the connect string by entering the Data Source Name
created in the ODBC Administrator.
If you do not enter a connect string or if you enter an “*” as
the data source name, the ODBC driver manager and you can
select the desired data source from the list box.

Connecting to ODBC
Alternative method — To connect to an ODBC

database from within MicroStation
1. Right-click the MicroStation icon and from the menu
that appears, choose Properties.
2. In the Properties dialog box, select the Shortcut tab.
3. At the end of the Target field, key in -wdodbc.
The Target field should now look something like this:
C:\Bentley\Program\MicroStation\ustation.exe -wdodbc
4. Click OK to save the changes and close the dialog box.
5. Start MicroStation by double-clicking the MicroStation icon.
6. In the Key-in window, key in DB = <data source name>
Starting MicroStation with the -wdodbc switch automatically

loads the configuration variables.
Accessing multiple DBMSs

In theory the ODBC standard allows an ODBC-enabled application to
access data from any DBMS that has an ODBC driver. In practice there
are several areas that cause problems when accessing multiple DBMSs.
The ODBC standard is based on SQL databases. All flat file

databases (Btrieve; dBASEII, III, and IV; Clipper; FoxPro; Excel;
and Paradox) must have an SQL layer that translates the ODBC
SQL call into a language the DBMS can understand. The problem
is that it is up to the ODBC driver vendor to implement the SQL
interpretive layer. The SQL syntax depends on how closely the
vendor follows ANSI and industry standards.
Refer to the Bentley website for a complete listing of

supported databases.
dBASE notes
File names cannot be more than eight characters. MSCATLOG
is the name of the mscatalog under the ODBC Xbase interface.

Connecting to ODBC
If you try to operate on the mscatalog table using MSCATALOG

as a table name, you will get ODBC Error 4101, “the connection,
statement, or query handle you provided is not valid.”
Column names cannot be more than 10 characters. In the

ODBC interface, column names that are greater than 10
characters will return an error.
Index files cannot contain expressions. The delivered Xbase GIS

example index files (and possibly some of your index files) have the
expression ‘FOR.NOT.DELETED()’. The Intersolv ODBC Xbase driver
cannot access information in a table that has an associated index file
that contains an expression; the expressions must be removed.
• Include an mslink column that is defined as a number or integer

• Ensure that your column names contain no SQL reserved words.
You can obtain a list of these from your database documentation.
• Ensure that your column names contain no special characters
like dashes (-), parentheses (), forward slash (/), backslash
(\), pound sign (#). Underscores (_) are acceptable.
• Do not use two-word column or table names. For example,
Owner Name is unacceptable but Owner_Name is acceptable.
Microsoft — SQL Server notes

The SQL Server does not recognize all ANSI SQL data types. The
following is the list that they will recognize: money, smallmoney,
int, smallint, tinyint, char(n), varchar(n), text, datetime,
smalldatetime, bit, timestamp, sysname, float, real, binary(n),
varbinary(n), image,numeric, decimal, integer.
The SQL Server does not recognize the following data

types: number and logical.
The SQL Server treats NULLs in a non-ANSI manner by default.
While ANSI standards specify that a column by default can accept
NULL values, in SQL Server you must specify a column as NULL for
it to accept NULL values. The NOT NULL option on columns works
as expected. This can lead to problems with Active Entity creation.
If a column in the Active Entity table does not have a value, the

Connecting to Oracle
active entity cannot be inserted into a table unless the create table
statement defined the no value column with the NULL option.
The user may alter the default behavior on NULLs in SQLServer
through the SQL Enterprise Manager. The default NULL
setting may be changed by editing the selected database, and
selecting the options tab. The Columns Null by Default check
box may then be set to the desired setting.
The user can also change this value through an SQL stored
procedure. The user must log into the SA account, or be the
owner of the database, and enter the following:
• sp_dboption database, “ANSI NULL default”, true sets

columns null by default.
• sp_dboption database, “ANSI NULL default”, false disables

columns null by default.
The Intersolv ODBC SQL Server driver does not support SQL
statements over 2400 characters at this time.
This section covers how to set up an Oracle database for
use with MicroStation.
For general information about the Oracle product family,

see the Oracle section on page 11-7.
General Procedure — Setting Up Oracle

1. Perform any indicated special setup steps in the “notes”
section for your system.
See Windows Notes.
2. Start Oracle on the server. This step must be performed before any
MicroStation session during which you will connect to an Oracle
database. See the “notes” section for your system. (The database
administrator is commonly responsible for starting Oracle.)

3. If the database resides on a remote server, create an alias through

Oracle SQL Net or Net 8 Easy Configuration utility.
4. Have the Oracle database administrator set up an Oracle user.
Make sure that the appropriate permissions are granted to the
user to allow select, update, delete, and insert permissions on
tables and create, alter and drop table permissions.
5. Test the connection to the remote server through SQL
Plus or SQL Worksheet to ensure that the Oracle client
has been configured correctly.
6. In SQL*Plus, run the supplied SQL script file, “mscat.sql” to
create the MSCATALOG Table (see page 13-31) and other
control tables referenced from within MSCATALOG. See
the “notes” section for your system.
To set up the GIS example database

1. In SQL*Plus, run the supplied SQL script file, “mscat.sql” located
in the “\Bentley\Program\MicroStation\database\oracle\”
directory to create the MSCATALOG Table (see page 13-31)
. See the “notes” section for your system.
2. Next, run the appropriate batch file for your operating system to
create the remaining tables. The batch files are located in the
“\Bentley\Program\MicroStation\database\oracle\examples\tables”
directory.
To connect to an Oracle database from

within MicroStation
1. From the Settings menu, chose Database > Connect.
The Connect to Database dialog box opens.
2. Set the Database Server to Oracle.
3. In the Connect String field, key in
<user_name>/<password>@<database_alias>.
4. Click OK.
If the MSCATALOG table does not exist, an alert box informs you
that you must create an MSCATALOG table in order to create
linkages from elements in the design to rows in the database.

Alternative method — To connect to an Oracle

3. At the end of the Target field, key in -wdoracle.
C:\Bentley\Program\MicroStation\ustation.exe -wdoracle
6. In the Key-in window, key in DB
=<user_name>/<password>@<database_alias>.
Starting MicroStation with the -wdoracle switch automatically

It is still possible to connect to an Oracle database by keying in |connect

<user_name>/<password> in the Key-in window, or by submitting the
statement “connect <user_name>/<password>” in the SQL Window.
To create the MSCATALOG table

1. Use SQL Plus, DBA or an Oracle graphical SQL tool.
2. Run the “mscat.sql” script file. At the SQL> prompt, enter:
@\Bentley\Program\MicroStation\database\oracle\mscat.sql
(This step assumes the MicroStation directory is
“\Bentley\Program\MicroStation”.)
3. Log off.

Connecting to Sybase
Alternative method — To create the

MSCATALOG table
1. From the Settings menu’s Database sub-menu, choose Setup.
An alert box opens to ask if you would like to create MSCATALOG.
MSCATALOG is created, and the Database Setup dialog box opens.
Windows Notes
For the batch files loadnt and loadwin to run correctly, the Oracle
7 or Oracle 8 Utilities must be installed.
For Windows NT, search for a file named sqlldr*.exe. located

in the “\orant\bin” directory in the Oracle 7 or Oracle 8
Utilities software. Make sure this matches the executable
name found in the loadnt.bat file.
For Windows 95, search for a file named sqlpad.exe. located in the
“\orawin\bin” directory in the Oracle Utilities software.
Connecting to Sybase
This section covers how to set up a Sybase database for use with
MicroStation. For general information on the Sybase product
family, see Sybase database on page 11-9.
To set up Sybase
1. Start the Sybase server.
2. Modify the supplied mscat.sql file to reflect the correct
database name. (It is delivered as “gis.”)

Connecting to RIS
3. Run the modified mscat script file to create the mscatalog

table. Do this by using the Sybase product “isql”:
isql -imscat.sql
4. Include any other parameters needed according to your
configuration (i.e., -S<servername>, -U<username>, etc.).
To connect to a Sybase database from

within MicroStation
1. From the Settings menu, select Database > Connect.
2. Set the Database Server to Sybase.
3. In the Connect String field, key in <database_name>
-U<username> -P<password> -S<servername>.
Alternative method — To connect to a Sybase

3. At the end of the Target field, key in -wdsybase.
C:\Bentley\Program\MicroStation\ustation.exe -wdsybase
6. In the Key-in window, key in DB=<database_name>
-U<username> -P<password> -S<servername>.
Starting MicroStation with the -wdsybase switch automatically

Connecting to RIS
This section covers how to set up RIS for use with MicroStation.

Connecting to RIS
General Procedure — Setting Up RIS

1. Create the schema. Refer to the RIS documentation.
2. Create the MSCATALOG control table and the control tables
referenced from within the MSCATALOG:
Use the RIS Load utility to run the supplied dump file,
“gis.dmp.” Refer to the RIS documentation. This creates sample
tables for the lessons in the Database Guide in addition to
MSCATALOG. This creates sample tables for the lessons in
this guide in addition to the MSCATALOG table (see Setting
Up Screen Form Loading Procedures).
3. Follow the setup procedures for the underlying database
product (see Oracle).
To connect to a RIS schema from within

MicroStation
1. From the Settings menu, select Database > Connect.
2. Set the Database Server to RIS.
3. Provide the <schema _name>.<password> as the connect string.
Alternative method — To connect to a RIS

schema from within MicroStation
3. At the end of the Target field, key in -wdris.
C:\Bentley\Program\MicroStation\ustation.exe -wdris
6. In the Key-in window, key in DB=<schema_name>[.<password>].
Starting MicroStation with the -wdris switch automatically


MS_LINKTYPE
MS_LINKTYPE
Linkages between design elements and the database can
be of any of the following types:
• ORACLE
• ODBC
• RIS
• SYBASE
The MS_LINKTYPE configuration variable definition controls
which linkage types the MicroStation database interface software
recognizes. By default, the delivered configuration files are
set to recognize all types of linkages.
Copying elements with attached linkages

When you copy an element that has database linkages, the
database linkages are copied with it. The linkage is written
as the type first specified in the MS_LINKTYPE variable,
regardless of the original elements’ link type.
For example, suppose you copied an element that has an ORACLE

linkage attached to it. If MS_LINKTYPE=ODBC, the linkage
that is attached to the new element (the copy) contains exactly
the same data. However, when you analyze the element, the
linkage is written as “ODBC Data Linkage” rather then “Oracle
Data Linkage”. It would also respect the Linkage Mode setting,
so for example, if Linkage Mode is set to New, the Oracle linkage
would be linked to a new row in the database.
The above example assumes MicroStation is connected to the database.

If not connected to a database, the element and database linkage are
copied as is, without regard to MS_LINKTYPE or Linkage Mode.
For more information about Linkage Mode, see Setting

Linkage Mode on page 13-41.

Linking Database Rows
to Elements
In this chapter, you will find procedures concerning linking information
in a database to elements in MicroStation.
Database Tools Available in MicroStation

There are two database interfaces available to the user for database
interaction. The first, Visual SQL Query Builder, is a GUI–based
interface. VSQL does not require users to key in the exact SQL query
statement to interact with the database. The SQL statement is built
as the user clicks on the table and columns and selects criteria for
queries from pull down menus. Execution of the auto-generated query
statement produces query results in the form. Values can be edited or
new rows can be added/deleted in the database by a click of a button.
The second is the SQL window and a series of tools from the Database
tool box. SQL (pronounced se-quel) stands for Structured Query
Language. SQL is a simple yet powerful language that is the industry
standard for database access and data manipulation.
Visual SQL Query Builder

The Visual SQL Query Builder provides a graphically intuitive
means of generating simple and complex queries and joining
tables. From the generated query, the Visual Query Builder
automatically builds form dialogs — dialogs containing simple
controls for interfacing to a database — which can be saved and
recalled when needed. Using the form editing tool, a form dialog
can be visually manipulated and reformatted.
The Visual SQL Query Builder is the default database query tool and
is available when Settings > Database > Query Builder is chosen.

Linking Database Rows to Elements
Visual SQL Query Builder dialog box overview
Visual SQL Query Builder dialog box overview

The Visual SQL Query Builder dialog box uses a simple graphical
means of generating query statements of varying complexity,
graphically generates and displays table joins, builds form
dialogs from generated queries, and allows you to save form
dialogs and to retrieve them for later use.
Selecting Query Builder from the Database menu opens the

Visual SQL Query Builder dialog box.
The Visual SQL Query Builder dialog box lets you easily build SQL
queries. It helps ensure proper syntax and reduces time consuming
key-ins for both novice and expert SQL users. The dialog box uses a
tab structure that separates and organizes the main query building
steps. The tab names follow the intuitive SELECT, WHERE, GROUP
BY, ORDER BY order with which most users are familiar.
The Visual SQL Query Builder also generates a database form dialog
from the query statement. The dialog form can be used to navigate
through a database table, and to query, insert, update and delete
rows in the table. The form can be saved for future use.

Building simple SELECT statements
The Standard Form Items dialog box is used to specify the control
items which appear on newly generated dialog forms.
To open the Visual SQL Query Builder dialog box, you must
be connected to a database.
This section starts with a simple SQL statement and sequentially

builds more complex statements, explaining how the Visual SQL Query
Builder is used to create SELECT statements, how it displays the
results to the user, and how the results are displayed in a dialog form.
All the examples in this section apply to the GIS database.
The following examples reflect different settings in the

Standard Form Items dialog box.
You can either type an SQL statement directly into the SQL Select
Statement field or you can proceed with following procedures and
have MicroStation generate an SQL statement for you.
To use the Visual SQL Query Builder to build the

following SELECT statement: SELECT parcel_no,
owner, parc_value FROM parcel
1. In the Visual SQL Query Builder dialog box, click Tables
or from the Tables menu choose Open.
The Select Table dialog box opens.

2. In the Table List option menu, choose MSCATALOG to

display the tables listed in the MSCATALOG table, or
choose All to display all project tables.
3. In the Select Table dialog box, double-click Parcel.
The Parcel dialog box opens in the work area on
the Select table page.
The Parcel dialog box contains all columns of the Parcel table.
4. In the Select Table dialog box, click Close to dismiss the dialog box.
5. To move the Parcel dialog box, left click the title bar, hold
the left mouse button down, drag the dialog box to a new
location, and release the mouse button.
This functionality will be very useful for visually generating table
joins. The following appears in the SQL Select Statement text box:
SELECT
FROM parcel
6. Double-click on the parc_owner, owner, and parc_value fields.

The SQL Select Statement updates to the following,
indicating that the query is complete:

SELECT parcel_no,owner, parc_value
FROM parcel
Double-clicking again on any of these selected fields will deselect

them, and the query statement updates to reflect the change.
7. Click the Execute button to review the results based on this query.
If Output > Form is turned on, the following form is generated.
In this example, the user can navigate forward and

backward through the Parcel table using the First, Next
and Last buttons. This dialog box, called a form, can be
saved and retrieved for future use.
If Output > Browser is turned on, the same results are displayed
in the Visual SQL Data Browser dialog box.
A maximum of 50 tables may be open at one time.
You can minimize or dismiss the large Visual SQL Query Builder
dialog box, leaving the smaller form dialog box active. This
can be useful if screen space is limited.
If you are working with a table that currently contains no rows of

data, turn off Execute Query on Open and Dataset Mode. This
will generate an empty form ready for data entry.

To use the Visual SQL Query Builder

to build the following query: SELECT
max(parc_area) FROM Parcel
1. Click ClearSQL, Clear All to clear everything.
2. In the Select tab page, click Tables or from the Tables
menu choose Open.
The Select Table dialog box opens.
The Parcel dialog box opens.
The SQL Select Statement now reads:

SELECT
FROM Parcel
4. In the Select Table dialog box, click Close.

5. Click the Functions options menu button, and select
Maximum Value of.
6. In the Parcel dialog box, double-click Parc_area.
The SQL Select Statement updates to the following,
indicating the query is complete:
SELECT MAX(parc_area)
FROM Parcel
7. Click the Execute button to review the results based on this query.
If Output > Form is turned on, the following form is generated.

If Output > Browser is turned on, the same results are displayed
8. Click ClearSQL, Clear All to delete the table and the SQL query.
Aggregate functions (Max, Min, Count, Sum and Avg) operate only
in Cursor mode. Clicking Execute places the Query Builder in
Cursor mode. The Dataset Mode check box is off.
Joining tables
A relational database typically consists of data stored in many
different tables. Joining tables allows you to obtain information
from more than one table at one time and enables you to choose
various data subsets of the joined tables. In a join, the currently
selected table is the Master Table and the table it is joined to is the
Lookup Table. The currently selected table name appears after the
FROM keyword in the SQL Select Statement text box.
A table join relationship can be established in the following way:
Short-term join — the join is defined in Visual SQL Query Builder

dialog box. The table currently selected is the Master Table, and
the second table selected is the Lookup Table. The join is completed
visually by left clicking a field in the Master Table, holding the
left mouse button down, dragging and dropping to the field in
the Lookup Table. A join graphic, a line with two end nodes, is
generated showing the fields that have been joined.

To delete the join, click on one of the join graphic nodes, and press Delete.
Insert, Update, and Delete database operations are not

supported for joined tables.
The Where tab page can be used to create compound Where
clauses with joined tables. For example:
To build a SELECT query which includes a

compound WHERE clause, use the Visual
SQL Query Builder to build the following
SELECT statement: SELECT parcel_no,owner,
house_num,str_name FROM parcel WHERE
parc_value >= 50000 AND parc_area >= 100,000
1. Click ClearSQL, Clear All to clear any existing tables.
2. In the Select tab page, click Tables or select menu
option Tables > Open Table.
4. In the Select Tables dialog box, click Close.
5. In the Parcel dialog box, double click on the Parcel_no,
owner, house_num, str_name fields.
The following displays in the SQL Select Statement text box:
SELECT parcel_no, owner, house_num, str_name
FROM parcel
6. Click the Where tab.

The Where tab page opens.

7. In the Available Fields list box, click the parc_value field.

The selected field appears in the Where Fields list box.
8. Click >= (greater than or equal to). In the Value text field,
type 50000 and press áReturnñ.
9. Click And to create the second WHERE clause.
AND displays in the Where Fields list box.
10. Click parc_area in the Available Fields list box, click
>= (greater than or equal to), enter 100000 in the Value
text field and press áReturnñ.
The entered operator and value display in the Where Fields list box.

11. Click Apply to add the clause in the Where Fields list box
to the SQL Select Statement text box.
The following displays in the SQL Select Statement text box:
SELECT parcel_no, owner, house_num ,str_name
FROM parcel
WHERE parc_value >= 50000 AND
parc_area >= 100000
The query in the SQL Select Statement text box is complete.

12. Click Execute.
If Output > Form is turned on in the Visual SQL Query Builder
dialog box, clicking Execute generates a dialog form.
If Output > Browser is turned on in the Visual SQL Query

Builder dialog box, clicking Execute generates a list (containing
the same information as in the dialog form) which is displayed

To edit any of the Where clauses, click on the clause in the Where
Fields list box. Dynamically change the field, operator, value
and AND/OR clause members as you would normally do when
building an SQL statement. Clicking Apply conforms the SQL
Select Statement to your changes in the Where Fields dialog box.
You can also delete the clause by clicking Clear.
If your selection in Available Fields is a character type, your

entry in the Value text field (for example, 100) is displayed with
single quotes around it in the Value column of the Where Fields
list box (is displayed as ‘100’, for example).
Common Operators do not work with character fields.
To build a SELECT query which includes

GroupBy and OrderBy clauses, use the Visual
SQL Query Builder to build the following
SELECT statement: SELECT owner, parc_area,
AVG(parcel_value) FROM parcel GROUP
BY owner, parc_area HAVING parc_area >
100,000 ORDER BY parc_area
1. Click ClearSQL, Clear All to clear any existing tables.
2. In the Select tab page, click Tables or from the Tables
menu choose Open Table.
4. In the Select Table dialog box, click Close.

5. In the Parcel dialog box, double-click on the Owner

and Parc_area fields.
The following is in the SQL Select Statement text box:
SELECT owner, parcel_area
FROM parcel
6. Click the Functions option button and choose Average Value of.
7. In Parcel, double-click parc_value.
The following text is in the SQL Select Statement text box:
SELECT owner, parc_area, AVG(parc_value)
FROM parcel
GROUP BY owner, parc_area
8. To edit the GROUPBY clause, click the GroupBy tab page.

The GroupBy tab page opens.

9. In the GroupBy Fields list box, click parc_area. Click the

> (greater than) Common Operator, enter 100000 in the
Value text field, and press áReturnñ.
10. Click Apply to generate the following statement:
SELECT owner, parc_area, AVG(parc_value)
FROM parcel
GROUP BY owner, parc-area, HAVING parc_area > 100000
11. To add the OrderBy clause, click the OrderBy tab page.
The OrderBy tab page opens.
12. In the Available Fields list box, click parc_area.

The selected field appears in the OrderBy Field text box.
13. Click Apply to add a OrderBy clause to the SQL Select
Statement text box.
The query in the SQL Select Statement text box is complete:
SELECT owner, parc_area, avg (parc_value),

Reviewing database attributes
FROM parcel
GROUP BY owner, parc_area having parc_area > 100000
ORDER BY parc_area
14. Click Execute to display the results of the query in either

a dialog form (Output > Form) or in the Visual SQL Data
Browser dialog box (Output > Browser).
Reviewing database attributes
Clicking the Review button from the created form allows you to
view a database record linked to an element that you identify on
the screen. Alternatively, if a form is not created, the key-in VSQL
REVIEW automatically generates a form for you.
The database record displays in a form dialog. The form buttons

(Insert, Update, Delete, etc.) displayed on the form dialog are those
chosen from the Standard Form Items dialog box (Settings > Forms).
Database form dialogs
MicroStation VSQL supports database operations including

query, update, review, and geolocate using dynamically definable
database dialog forms. These forms are generated using the Visual
SQL Query Builder. Database form dialog controls allow users
to create, edit and save database forms after first interactively
defining form contents and dialog controls.
Database forms support row navigation operations, including
find first row, last row, next row, previous row, and row count.
Database update and query operations include query execute,
row insert, row update, and row delete. Database forms support
integrated database and graphics operations including database

review, and locate. The form may also be used to attach and
detach linkages from graphical elements.
After generating the form, the user can customize the organization
of the form and associated controls using the visual editing tools
in the Visual SQL Query Builder. Individual dialog controls can
optionally be set to read-only in the case that forms are intended to
support query operations only. (This is accomplished by selecting
Forms from the Settings menu, and turning off Insert Row Button,
Delete Row Button and Update Row Button.) Once a form has been
created it can be used to query and review database attributes
using “query by example” functions that allow users to enter values
and operators (“\>”, “<”) directly into form fields.
Only the fields selected in the <TABLENAME> dialog box appear in

the results section of a database dialog form. Instead of getting all
rows in a table, the form dialog provides only the fields needed by the
user. This ability to customize data display and editing enhances
user productivity by reducing the quantity of data to a manageable
scale. The control of database resources in this way enables the
transformation of raw data into useful information.
You can minimize or dismiss the Visual SQL Query Builder,

leaving the form dialog active.
The following description assumes that your form dialog
contains all possible items.
To create a new form dialog containing all items

1. Choose Settings > Forms.
2. In the Standard Form Items dialog box, turn all
items on, and click OK.
3. Create a new form as described in this chapter. For example, see
Building Simple SELECT Statements on page 13-3.

The Query text field is present because Query Multiline was turned
on in the Standard Form Items dialog box.
To perform a review from a form dialog

1. In the form dialog, click Review.
2. Identify an element that has database attributes from the
same table as the open form dialog.
3. Accept the element.
If the element that you select does not contain a linkage to a row in the
currently selected table, no information will appear in the form dialog.

Locating linked elements
The locate functionality can be enhanced by adding a column called

mapid (integer) to the attribute table and adding a table called maps
to the database. This allows you to locate graphic elements linked to
the current database row that reside in different design files. The
design file that the graphics are linked to is attached as a reference
file. Without this additional column and table, the locate function
will return “No elements linked to the current row” when the Locate
button is clicked. The maps table can be created as follows:
1 . Create table maps (mslink integer, mapname char(30))
2 . In the maps table, you must add a entry for every design file
containing linked graphics and assign that map an mslink number.
In the attribute table, you must add the mslink number that you have
assigned to the map to every row that is linked to graphics in the map.
To display the design element linked to one

of the records resulting from the SELECT
statement: SELECT * FROM parcel
1. Open either "cd9.dgn" or "cd10.dgn" (located by default in
“Bentley\Workspace\projects\tutorials\intro\dgn”).
These design files have linkages to GIS database tables.
2. Build the Select statement using the Visual SQL Query Builder.
(See Building Simple SELECT Statementspage 13-3.)
3. Turn on Output > Form.

4. Click Execute to create the form dialog.

5. In the form dialog, click Next to step through the list
of query responses until you find a particular parcel
in which you are interested.
6. Click Locate to display the element corresponding to
the displayed query result.
You are prompted to identify a view in which to locate
the parcel element.
7. Enter the view in which you want the parcel element displayed.
If the parcel record selected corresponds to a parcel in an
open map, the parcel element displays centered in the
selected view, with its number circled and highlighted.
Zoom out to see where the element is.
If the parcel record selected is not linked to a graphic element
in the active design file, the following message is displayed:
“No element linked to current row.”
In SQL, in this context, * means ‘all columns’ or ‘all attributes’.
Opening, editing and saving form dialogs
To open a saved form

1. From the Forms menu, choose Open.
2. In the Open Form dialog box, select a directory, and
select a form filename to open.
3. Click OK.
Alternative method — To open a saved

form using a key-in
1. Key in: VSQL FORMS OPEN <form_name>
This assumes that the form has been saved in the default directory or
the directory set in the configuration variable MS_DBDIALOGRSC.
If the form has been saved in another directory, the full path to
the form must be provided in the key-in.

To resize a form dialog item on the form

1. From Visual SQL Query Builder’s Form menu, choose Edit.
The Edit Form dialog box opens.
2. Select the file of the form dialog you want to modify, and click OK.
The Builder dialog box, Builder’s Tools tool box, and
the form dialog open.
3. On the form dialog, click the control to resize.
Handles appear at the corners of the button.
4. Drag and drop an edge of the button.
The button is resized.
5. Click anywhere inside the form dialog.
The handles disappear.
This procedure assumes you have saved the form dialog

you want to modify.
To resize a form dialog item using the

Builder dialog box
3. In the Builder dialog box, in the bottom list box, in the Label
column select the label of the control to resize.
In the form dialog, handles appear at the corners
of the push-button.
4. In the text boxes under the list box you are working with, change
the X and Y values if you want to change the position of the button,
change Wdth if you want to change the width of the push-button, or

change Hght if you want to change the height of the push-button.

After each text box change, click <Enter> to apply the change.
The button is resized.
5. Click anywhere inside the form dialog.
The handles disappear.

you want to modify.
To interchange the positions of controls

on a form dialog
3. In the form dialog, drag and drop the two buttons in
order to interchange their location.
4. In the form dialog, click the window menu button to
dismiss the form dialog.
An Alert box opens asking you whether you want to
save your changes.
5. Click Yes to save your changes, click No to discard your changes,
and click Cancel to dismiss the Alert box.

you want to modify.
To add an item to a form dialog

1. Click a button on the Builder’s Tools tool box.
2. Click on the Form dialog to place the new item.

To delete an item from a form dialog

1. Click on an item in the Form dialog.
2. In the Builder dialog box, select the menu option Edit > Delete.
To save or to further customize the form

generated from the Visual SQL Query Builder
1. From the Visual SQL Query Builder’s Forms menu, select Save As.
2. Into the Save Form dialog box (a standard file selection dialog
box, having its search filter preset to .rsc), select a directory
and type a filename for the form to be saved.
3. Click OK to save the open form dialog.
To save a form dialog, its SQL query must be in the Visual SQL
Query Builder dialog box’s SQL Select Statement text box.
Opening and saving query statements

To open and save query statements, proceed as follows:
To open a query statement

1. From the Query menu, select Open.
2. Select a file with a .sql extension.
3. Click OK.
To save a query statement

1. From the Query menu, select Save As.
2. Type in a filename.
3. Click OK.

Using SQL
Using SQL
SQL statements can be used to interactively query a database
directly from within MicroStation.
All SQL statements recognized by the database software

are supported, including:
SELECT Query database tables.

UPDATE Edit rows in a table.
DELETE Delete rows.
INSERT Add new rows.
CREATE Define a new table and add
it to the database.
DROP Delete an existing table.
SQL statement syntax is covered in SQL statements (see page 13-22) .
SQL statements
The following sections contain descriptions of some of the more
powerful SQL statements that are supported by the database interface.
Literal expressions used in assignments and comparisons can be

of character, numeric or date format. Character strings are single
quote delimited. In general, dates can be queried as follows:
• For ODBC — SELECT* FROM <table> where

<date_field> > #01/01/2000#
The date format through ODBC depends upon the
setting of the MicroStation configuration variable
MS_DBODBCDATEFORMAT. It is set to mm/dd/yyyy by
default. The variable is stored in the "odbc.cfg" file located in
the “\MicroStation\config\database\” directory.
• For Oracle (direct connection) — SELECT* FROM <table>
where <date_field> > ’21-DEC-00’
The date format in Oracle is dependent upon the
NSL_DATE_FORMAT setting. You must use the following
statement keyed in through the SQL Window or the SQL

SQL statements
statement portion of VSQL to alter the format (substitute

the format you require for mm/dd/yyyy):
alter session set nls_date_format = ’mm/dd/yyyy’
It is recommended that you use VSQL to create the SQL for the query
as it will assist you in properly delimiting the date field.
So the following SELECT statement would be valid for ODBC:
SELECT * FROM mytable WHERE mychar = ’Character’ AND myfloat

= 3.5 AND myint = 4 AND mydate = DATE (#01/01/2000#)
SELECT
SELECT á* | <column_name_listñ FROM table WHERE
<condition_list>
Used to query the database. Condition_list can contain any number of

comparisons separated by AND or OR operators. The comparisons
need not be equivalences (that is, <, >, <=, etc. are valid).
UPDATE
UPDATE <table> SET <assignment-list>
Used to edit column values.
DELETE
DELETE FROM <table> [WHERE <condition_list>]
Used to delete rows.
INSERT
INSERT INTO table <column_name_list> VALUES <expression_list>

SQL statements
Used to insert column values. If column_name_list is omitted, there

must be an expression for each column in the table and it must be
listed in the order in which the columns were added to the table.
CREATE TABLE
CREATE TABLE table <column_name_type_list>
Used to create a table. Column_name_type_list is a

comma-delimited list of expressions of the form: <<column_name>
<column_type>>. For example:
CREATE TABLE mytable (name char(10), age integer)
creates a table with a name column of 10 characters and

an integer age column.
Data types can be any ANSI SQL data type. Refer to

any SQL reference for a list.
DROP
DROP TABLE table
Used to drop a table from the data dictionary and to physically

delete associated data and index files.
CREATE DATABASE
CREATE DATABASE <database_name>
Used to create a database.
COMMIT
Used to explicitly request MicroStation to commit statements

to the database software for processing. See SESSION
AUTOCOMMIT [OFF|ON].

Specific SQL Window key-ins
ROLLBACK
Used to undo all statements to the last commit point. See
SESSION AUTOCOMMIT [OFF|ON] .
Specific SQL Window key-ins

The following section contain descriptions of MicroStation-specific
SQL Window key-ins.
CONNECT
Used to connect to an Oracle database. Either key in DB= or use
Settings > Database > Setup as described in Database Setup dialog box .
DISCONNECT
Used to disconnect from an Oracle database.
RELOAD
Used to force MicroStation to reread mscatalog and update the

copy of the table it maintains internally. (Changes to mscatalog
resulting from SQL statements typed and submitted by the
user in the SQL Window are not automatically reflected in
MicroStation’s internal copy of the table.)
Using the SQL Window

The SQL Window is used to submit SQL statements and
to review the results.

Using the SQL Window
To open the SQL Window

1. Key in SQL.
The SQL Window has a large section at the top for
reviewing SQL queries and a smaller field at the bottom
for submitting SQL statements.
The user can also enter SQL commands preceded by the pipe
symbol “|”in the MicroStation key-in window.
To submit a SQL statement

1. In the SQL Window, type the SQL statement. The statement
can be typed as a continuous string with automatic word wrap
or you can press áReturnñ at the end of each line.
Literal expressions used in assignments and comparisons
can be of character (char), numeric (number). Character
strings are single quote delimited.
2. Click the Submit button.
Retrieved database information is presented one row at a time.
You can use the scroll bar if the data exceeds the window size.
3. (Optional) — To advance between retrieved rows,
click the Next button.

Command files
Command files
If you submit a particular SQL statement frequently, you can save it
in a command file for easier submission. A command file is simply a
text file into which a SQL statement has been placed. While the
file can contain only one statement, the statement can be continued
on multiple lines. The default file extension is “.sql.”
Some database interface key-ins require SQL statements, such as

ACTIVE ENTITY (AE=). Unlike actual SQL statements, these key-ins
cannot be submitted in the SQL Window; they must be keyed in the
Key-in Window. Like all MicroStation key-ins, these key-ins can also
be activated from a script file with the key-in @<SCRIPT_FILE>. (The
file extension cannot be omitted.) See Key-in Scripts on page 9-1.
To create a command file

1. In the SQL Window, type the SQL statement you want to save.
2. From the SQL Window’s File menu, choose Save As.
The Save SQL Command File dialog box opens.
3. In the Name field, key in the desired filename.
4. Set the destination Directory as desired.
To submit a SQL statement stored in

a command file
1. From the SQL Window’s File menu, choose Open.
The Open SQL Command File dialog box opens.
2. Select the file that contains the desired statement.
3. Click OK.
4. When the statement is displayed in the SQL Window,
click Submit to execute the query.

Manually committing SQL statements
Alternative method — To submit a SQL statement

stored in a command file
1. In the SQL Window, submit @<file_name>.
The “.sql” file extension is the default.
Manually committing SQL statements

SQL statements are generated by MicroStation each time
you use certain database tools and key-ins. For example,
MicroStation generates a SQL INSERT statement when you
use the Attach Active Entity tool with Linkage Mode set to New
(see Setting Linkage Mode on page 13-41).
By default, MicroStation immediately commits SQL statements

to the database software. In an alternate mode, MicroStation
commits statements only when your input necessitates the addition
of a row to a database table. The process of adding rows requires
the database software to lock tables, and commitment is required
to release those locks. The alternate mode can be useful when it is
desirable to be able to undo uncommitted SQL statements.
To activate the mode in which MicroStation does

not automatically commit SQL statements
1. In the Key-in window, key in: SESSION AUTOCOMMIT OFF
To explicitly request MicroStation to commit

statements when AUTOCOMMIT is set to OFF
1. In the SQL Window, submit: COMMIT
To undo (negate) the effect of all statements

to the last commit point
1. In the SQL Window, submit: ROLLBACK

Creating Tables
To reactivate the default mode

1. In the Key-in window, key in: SESSION AUTOCOMMIT ON
You must type COMMIT before exiting MicroStation when the

AUTOCOMMIT mode is set to OFF. Otherwise uncommitted
transactions will be discarded.
Creating Tables
Creating a table is as simple as submitting a standard SQL
CREATE TABLE command.
To create a table
1. In the SQL Window, submit a statement in the following
form: CREATE TABLE table_name(Column_name_1
Column_spec_1,Column_name_2 Column_spec_2,…)
Column specifications can be any type supported by SQL,
including char, numeric, and date.
The only requirement to enable a row to be linked to an element is

that one of the columns in the table be named mslink and the table
has an entry (tablename and entity number) in the mscatalog.
For example, suppose in the utility map example on which the

lesson at the beginning of this chapter is based, you must create
a new table for the purpose of assessing real estate taxes. You
might submit the following CREATE TABLE statement: CREATE
TABLE assessor(clt_no char(30), as_val number(10),tax_rate
number(10,4),mslink number(10))
The resulting table would be created (sample data is shown):

Note the common column, clt_no, between the new table and
the already existing parcel table.

mslink column
assessor
clt_no as_val tax_rate mslink
119-LA 9 180,000 0.0500 37
119-LB 36 144,000 0.0500 38
119-LB 35 180,000 0.0500 39
parcel
mslink clt_no house_ name value area
num-
ber
1 119-LA 220 BRIDGE- 9000 16,036
9 WATER
RD
14 119-LB 8717 KILDARE 7200 16,668
36 DR
15 119-LB 8713 KILDARE 9000 16,306
35 DR
mslink column
The mslink column serves as a primary key for the table. This means
that any row can be uniquely specified solely by its mslink column value.
Key index
When a SELECT, UPDATE, or DELETE statement is submitted, the
specified table is searched. Indexes are used whenever available to
speed the search. An index is a linked list that contains only the
column of interest and its row number in the table. Indexes are
optional, but they greatly improve performance. Any column in a table
can have its own index. Of course each index takes disk space, so you
need to make a trade-off between files size and performance.

MSCATALOG Table
As the mslink column is the primary key for a table, it makes sense
to create an mslink index. You must create this index using your
database program. Bentley recommends you create this index as a
unique index and do not allow NULLS in the MSLINK column.
MSCATALOG Table
Before you delve too far into creating tables, you need to have a
good understanding of the MSCATALOG table. It is a special
table that tells MicroStation information about the database tables
available. It is opened every time you connect to a database and
contains a row for each table that is linked to the design. There
is only one MSCATALOG table for each database.
Any table in a database that will be associated with elements

must have a corresponding row in the MSCATALOG. However,
through SQL statements, any table in the database can
be accessed from MicroStation even if it does not have a
corresponding row in MSCATALOG.
mscatalog structure
The MSCATALOG table has the following structure:
Column Type(width) Description
tablename char(32) table name
entitynum number(10) unique entity or table

number
screenform char(64) screen form name
reporttable char(64) report table name
sqlreview char(240) default SQL review

request
fencefilter char(240) default SQL fence
filter
dastable char(32) displayable attributes
table name

mscatalog structure
Column Type(width) Description

formtable char(64) table used to locate
screen form (optional)
nextocc (RIS database This column is
interface only) only used for RIS
connections and
should not be added
to the MSCATALOG
table for any other
database connection.
tablename column
The tablename column in the MSCATALOG table contains the names
of the tables in the database that are to be linked to elements. The
table names must be added to the tablename column before linkages to
elements are made. This is a required entry in the MSCATALOG table.
entitynum column
The entitynum column in the MSCATALOG row for a particular table

contains the entity number of the table. The entity number is a
positive integer from 1 to 65535 that uniquely identifies the table to
the database; each table used with a design must have a unique entity
number. This is a required entry in the MSCATALOG table.

mscatalog structure
screenform column
The screenform column in the MSCATALOG row for a particular table
specifies the default screen form, used in conjunction with the Review
Database Attributes of Element tool, to review the database attributes
of elements linked to rows in the table. If the optional formtable column
(see page 13-34) exists in MSCATALOG, that column is examined to
attempt to locate a screen form to be used instead of the default screen
form. The screenform column will be used for both review and editing if
formtable is empty. This is an optional entry in the MSCATALOG table.
Screenforms are only supported with Oracle and Access forms

through a basic macro DDE link.
reporttable column
The reporttable column in the MSCATALOG row for a particular
table contains the name of the report table that can be created with
the Generate Report Table tool to report on the database attributes
of elements linked to rows in the table. This column is ordinarily
loaded with the key-in ACTIVE REPORT (RS) but can be entered
manually. This is an optional entry in the MSCATALOG table.
sqlreview column
The sqlreview column in the MSCATALOG row for a particular

table contains the SQL SELECT statement that is submitted with
the Review Database Attributes of Element tool to review database
attributes of elements linked to rows in the table. If this SQL
statement is entered incorrectly or the column entry contains blank
spaces, the SQL Review window is blank when the database linkages
are reviewed. When this field is left empty, the default SQL statement:
SQL Statement Select * From <tablename> is executed. This column is
ordinarily loaded with the key-in ACTIVE REVIEW (RA=) but may be
entered manually. This is an optional entry in the MSCATALOG table.
fencefilter column
The fencefilter column in the MSCATALOG row for a particular table

contains the SQL SELECT statement that determines which elements

mscatalog structure
linked to rows in the table are selected for fence operations. This
column must be loaded with the key-in DEFINE SEARCH (DS=) to
function properly. This is an optional entry in the MSCATALOG table.
dastable column
The dastable column in the MSCATALOG row for a particular
table specifies the displayable attributes table that is used to
determine which attributes of elements linked to rows in the
table display in displayable attribute text nodes and whether
screen forms are used to display the attributes.
Each row in a displayable attributes table (see the following table)

specifies a displayable attribute type number and definition.
Column Type(width) NULLs

dastype number(3) no
formname char(240) yes
sqldas char(240) yes
The formname column for a particular displayable attribute
type specifies the screen form used to display attributes.
The sqldas column specifies a SQL SELECT statement that
selects the attributes for display.
For more information about displayable attribute text nodes, see

Displaying Database Attributes in the Design on page 14-2. This
is an optional entry in the MSCATALOG table.
formtable column
The optional formtable column in the MSCATALOG row for a
particular table specifies the forms table that is used to locate
screen forms for reviewing and editing database attributes of
elements linked to rows in the table.
The forms table has the following structure:

Creating and maintaining MSCATALOG
Column Type(width) NULLs

tablename char(32) NO
type char(64) NO
formname char(64) NO
The type column can have a value of either review or edit,
but they must be in lower case.
When you use the Review Database Attributes of Element tool, if Forms
is set to Text screen, the screen form is located by first looking at the
formtable column in MSCATALOG form for the appropriate table. If a
form table is specified and it exists, its contents are searched for the
name of the form to use. If a form name is found for the table for the
current linkage and its type is review, this form is used.
If a form table is not found or does not exist, the form

specified in the screenform column of MSCATALOG is used
for review and edit operations.
VSQL forms may be saved and the name entered in the formtable
column. When forms are set to text screen (Settings menu > Database
> Dialog), the VSQL saved form will open instead of the SQL Window
when the Review Database Attributes tool is used.

The SQL statement for creating MSCATALOG is in the
SQL command file, “mscat.sql.”
To create the MSCATALOG table

An alert box opens to ask if you would like to create MSCATALOG.
MSCATALOG is created, and the Database Setup dialog box opens.

To create an attribute table in the database

The Database Setup dialog box opens.
2. From the dialog box’s Table menu, choose Create.
The Create Table dialog box opens.
3. In the Table Name field, key in the name of the table.
The Insert Column dialog box opens.
5. In the Column field, key in the name of the first column.
6. From the Type option menu, choose the column’s data type
— Character, Integer, Real, or Date.
7. If Type is Character, key in the field width (number of
characters) in the Width field.
or
If the type is integer, key in the total number in the Width field.
or
Otherwise, skip to step 8.
If Type is Real, key in the total number of digits in the
Width field and the number of digits after the decimal
point in the Decimal field.
8. Click the OK button to return to the Create Table dialog box.
9. For each additional column, repeat steps 4-8. (To edit or delete a
previously defined column, use the Edit and Delete buttons.)
To add a table to the MSCATALOG table

2. From the dialog box’s Table menu, choose Add to MSCATALOG.
The Add Table to MSCATALOG dialog box opens.

3. From the Table Name option menu, choose the table

to add. This will become the tablename value in the
MSCATALOG row for the table.
4. In the Entity Number field, key in a unique entity number
for the table. This will become the entitynum value in
the MSCATALOG row for the table.
To delete a table from the MSCATALOG table

2. In the Tables list box, select the table to delete.
3. From the dialog box’s Table menu, choose Delete
from MSCATALOG.
To drop a table from the database

2. From the dialog box’s Table menu, choose Drop.
The Drop Table dialog box opens.
3. From the Table Name option menu, choose the table to drop.
To add a new row (for a new table) to

the MSCATALOG table
1. In the SQL Window, submit: INSERT INTO MSCATALOG
VALUES (’<table_name>’,<entity_number>,’<screen_form>’,
’<report_table_name>’,”,”,”,”)
or
INSERT INTO MSCATALOG (tablename,
entitynum, screenform, reporttable) VALUES

Database Tools
(’<table_name>’,<entity_number>,’<screen_form>’,
’<report_table_name>’).
If using the first syntax, all columns must be inserted; notice
that the last four values are blank.
2. In the SQL Window, submit: RELOAD
This will refresh the MSCATALOG.
For example, to insert a row into MSCATALOG for the sample
assessor table, you might submit (for step 1):
INSERT INTO MSCATALOG VALUES

(’assessor’,4,’as_screen’,’as_report’,”,”,”,”)
If using the above method, you must reload the database manually
(key in RELOAD) for changes to take effect.
Database Tools
The tool box is operated in the same manner as tool boxes that
contain MicroStation’s drawing tools.
To open the Database tool box

1. From the Tools menu, choose Database.

Creating Linkages
Creating Linkages
Use the Attach Active Entity tool in the Database tool box to create
linkages from elements in the design to rows in the database.
To create a Linkage(s)
1. Define the Active Entity (see Defining the Active
Entity on page 13-39.)
2. In the Database dialog box, set Linkage Mode (see Setting Linkage
Mode on page 13-41.) Use the Attach Active Entity tool to attach
an element(s) to the row designated as the Active Entity.
Defining the Active Entity

The row that is designated as the target row to be attached to an
element when a linkage is created is called the Active Entity.
It becomes the only row in a special table named AE. The Active
Entity can be thought of as a temporary holding place for data
multiplication. It can be created several different ways:
• It can be defined graphically with the Define Active

Entity Graphically tool.

Defining the Active Entity
• It can be created directly with the ACTIVE ENTITY (AE=) key-in.

• It can be located and copied from a seed row in the existing
table with the FIND (FI=) key-in.
To define the Active Entity graphically by

using the database tool
1. Select the Define Active Entity Graphically tool.
2. Select an element that is already linked to the database.
This element should have a linkage to the database row that
you wish to attach another element.
3. Select the element to receive the linkage.
To directly define the Active Entity by key-in

1. In the Key-in window, key-in: AE=INSERT INTO
<table_name>(<column_1>, <column_2>,…)VALUES
(<value_1>,<value_2>…)
or
ACTIVE ENTITY INSERT INTO <table_name>(<column_1>,
<column_2>,…)VALUES (<value_1>,<value_2>…)
Here you are creating the Active Entity, in the AE table,
with the same data structure as table_name. This active
entity will create a new row in the database table and is
only valid in the new linkage mode.
The linkage mode will determine whether the existing row is

linked to the graphic (duplicate mode) or a new row is created
using the current row as a seed row (new mode).
To define an Active Entity from a seed row

1. In the Key-in Window, key in: FI=SELECT * FROM <table_name>
WHERE <column_name>=’<value>’
or
FIND SELECT * FROM <table_name> WHERE
<column_name>=’<value>’
This key-in will create the active entity from an existing
row in the attribute table. Depending on the linkage mode

Setting Linkage Mode
(new or duplicate), the linkage will be created the existing

row, or a row will be added to the table.
The Show Active Entity tool is used to check the values
in the Active Entity.
Editing the Active Entity

You can edit the Active Entity from within MicroStation before linking
it to an element using an SQL UPDATE statement.
Depending on Linkage Mode, which is set in the Database dialog box,

editing the Active Entity can change a row in the database. If Linkage
Mode is set to New, the Active Entity is a prototype record; editing the
Active Entity does not affect any rows. However, if Linkage Mode is
not set to New, editing the Active Entity changes the corresponding
row. For more information, see Setting Linkage Mode on page 13-41.
To edit the Active Entity using an SQL

UPDATE command
1. In the SQL Window, submit: UPDATE AE SET <column>
= <value>,<column> = <value>, …
For example, if you were working with the parcel table you
might submit: UPDATE AE SET house_num = ‘8716’,str_name
= ‘KILDARE DR’, value = 8000

Linkage Mode, which is set in the Database dialog box, determines
how the Active Entity is treated when an element is linked to it. When
Linkage Mode is set to None, no linkages can be created.

New linkage mode

Use New linkage mode when you require a unique row for each
linkage, such as in the case of land parcels on a map. In New
mode, the Active Entity is actually a “prototype row” that does
not need to represent an existing row in the table.
Each time a linkage is created in New mode, a copy of the Active

Entity is appended to the table as a new row. The element is then
linked to the new row. If you operate exclusively in New mode
when establishing linkages, you can be sure that each element you
link has a corresponding unique row in the database.
Duplicate linkage mode
In Duplicate linkage mode, each designated element is linked to the

same row as long as that row remains the Active Entity. This is useful
when it is necessary only to associate elements with a generic “row
type” rather than to a particular occurrence of that row type.
For example, in a circuit board design, it may not be desirable for

electrical components like resistors and capacitors to be linked
with unique rows. Accurate part counts are still possible even
if resistors of the same type “share” rows.
Information linkage mode

Information linkage mode is identical to Duplicate mode except that
a special bit is set in each linkage. This distinction is important to
application software that examines this bit when processing linkages.
Information linkages cannot be reported, and they do not cause table
rows to be added or deleted when the linked element is copied.

Attaching linkages to cell libraries
To set Linkage Mode

1. From the Settings menu, choose Database > Dialog.
The Database dialog box opens.
2. From the Linkage Mode option menu, choose the desired mode
— None, New, Information, or Duplicate.
Attaching linkages to cell libraries

Applications frequently need to associate database information with
cells. The Cell Link dialog box is used to link a cell library with
an existing database table by attaching database linkages to the
library cells. This makes it possible to place cells in the design
with a database linkage already established.
Oracle Notes
This section pertains specifically to using the Oracle database interface.
Editing the Active Entity

If Linkage Mode is set to New, the EDIT AE key-in can be used only to
add data to the Active Entity, not to edit previously existing data.
RIS Notes
This section pertains specifically to using the RIS database interface.

nextocc MSCATALOG column

Only the RIS database interface recognizes the nextocc
column in MSCATALOG.
The nextocc column contains the next available mslink number

for the table represented by a particular row in MSCATALOG.
If a nextocc column exists, MicroStation uses it to obtain the
maximum >mslink value (nextocc – 1) and to assign new mslink
numbers. If a nextocc column exists, it must be used for all tables
in MSCATALOG; it cannot be blank for any row.
Nextocc has the advantage that a new mslink number

can be acquired as follows:
1 . Get the value of nextocc for a particular table, call it mytable,

and store it in a variable called currOcc.
2 . Submit the following SQL statement:
UPDATE MSCATALOG SET nextocc = currOcc+ 1 WHERE

tablename = ’mytable’ AND nextocc = currOcc
If another application has updated MSCATALOG between

steps 1 and 2 and in doing so invalidated currOcc, reissue step
2 with currOcc = currOcc + 1. When step 2 succeeds, the value
currOcc can be used to add a row to mytable.
This approach eliminates the need to lock the table, get the
maximum mslink value, insert the record, and unlock the table
(hence, ending the transaction in which the lock was issued). This
approach may also be faster than some max (mslink) operations
on some relational databases, although with proper indexing most
databases perform such operations fairly quickly.
If there is a nextocc column in MSCATALOG, the RIS interface

assumes the value is valid. No validation is done. You must
initialize the nextocc column.
The nextocc approach may be dangerous for some users. This

approach assumes that each user adding a record to a table clears
the mslink number though the nextocc column in MSCATALOG. If
an application on the network adds rows to the table without regard

to the nextocc column in MSCATALOG, MicroStation may later

try to insert a row into the table and assume the value in nextocc
has not been used. Mslink columns should always be uniquely
indexed so this operation will fail rather than cause duplicate mslink
numbers. If for some reason the mslink column is not uniquely
indexed, duplicate mslink numbers can result.


Querying and Maintaining
the Database
In this chapter you will find procedures concerning querying the
database, reviewing database attributes, detaching linkages,
and otherwise maintaining the database.
Reviewing Attributes
Reviewing the database attributes of elements is the cornerstone of
the database interface. You can graphically query the database to
review attributes using the Review Database Attributes of Element
tool. The attributes can be displayed for review in the SQL Window
or in screen forms designed with the database software.
Setting attribute review selection criteria

Attribute review selection criteria can be set and saved in the sqlreview
column of the row in MSCATALOG for the desired table. The sqlreview
value applies only to data retrieved for display in the SQL Window.
To check the selection criteria for all tables (the

sqlreview values for all tables listed in MSCATALOG)
1. In the Key-in window, key in:ACTIVE REVIEW $
or
RA=$
The sqlreview value for the first table is displayed
in the SQL Window.
2. Click the Next button to review the sqlreview values
for successive tables.

Querying and Maintaining the Database
Displaying Database Attributes in the Design
To change the selection criteria

1. In the Key-in window, key in:ACTIVE REVIEW
<SQL_SELECT_statement>
or
RA=<SQL_SELECT_statement>
For example, to review all columns in a table, key in:RA=SELECT
* FROM <table_name>
This is the default for any sqlreview column with a NULL value.
To review specific columns, key in:RA=SELECT

<column1>,<column2>,… FROM <table_name>
Selection criteria can also be modified by directly submitting a

SQL UPDATE statement (through the SQL Window) or using the
MSCATALOG dialog box. Submitting a SQL UPDATE statement
for this purpose can be confusing because the statement must have
a SQL SELECT statement embedded as a string.
Verify that the SQL statement is valid before updating the SQL
review column. No validation is done on this column, so if there
is a mistake in the syntax, the SQL review window will display
with no information and no error message.

You can place a copy of some or all of an element’s database attributes
as text in the design. The process of displaying attributes is really
quite simple: An empty text node is placed and then designated as
a displayable attribute text node. Selected attributes are loaded
into the displayable attribute text node based on an SQL SELECT
statement. If the database information changes or you change
the columns selected by the SELECT statement, you can update
the design by simply reloading the text nodes.
Different types of displayable attribute text nodes can be defined

to display different combinations of attributes in various formats.

The displayable attribute table specifies the display format for

each type of displayable attribute text node.
The SQL SELECT statement for the displayable attribute type defined
in the column determines the list of columns that are loaded. If
no SELECT statement is defined, SELECT * is used.
General Procedure — Displaying Attributes

1. If the desired display format is not yet specified as a
displayable attribute type, create a type. See To create
a displayable attribute on .
2. Use the Place Text Node tool to place text nodes as placeholders
for the attributes that will be displayed.
3. Use the Attach Displayable Attributes tool to designate the text

nodes as displayable attribute text nodes of the desired type.
4. Use the Load Displayable Attributes tool to load the attributes
for display in the displayable attribute text nodes.
5. If you change the displayable attribute type specification
or the values of the displayed attributes and you want to
reflect the changes in the design, reload the attributes using
the Load Displayable Attributes tool.
To create a displayable attribute type

1. In the SQL Window, submit: INSERT INTO
<displayable_attribute_table> (dastype, sqldas) VALUES
(<type_number>, ’<SQL_SELECT_statement>’)
The displayable attribute table contains two columns,
dastype (number), and sqldas (text).
Alternately, this record may be inserted through VSQL.

Detaching Linkages
To modify a displayable attribute type

1. In the SQL Window, submit: UPDATE
<displayable_attribute_table> SET sqldas =
’<SQL_SELECT_statement>’ WHERE dastype = <type_number>
Alternately, this can be updated through VSQL.
To change the appearance (as opposed to the arrangement) of attributes

in a displayable attribute text node, use the Text settings box (Element
menu > Text) and the Change Text Attributes tool.
Detaching Linkages
The Detach Database Linkage tool is used to detach linkages from

elements or sets of elements using the Use Fence setting operation.
Linkages of the type(s) specified in the MS_LINKTYPE configuration
variable definition are removed. Linkages of other types and
application user data are not disturbed. The Delete Linked Database
Rows setting in the Database dialog box determines whether the row(s)
that were attached to a particular element are deleted from the table.
To prevent accidental deletions of elements that are attached to

database information, turn on the user preference Block Database
Undeletes in the Database category of the Preferences dialog box.
Detaching linkages from cells

To detach linkages from a component element of a cell, you must
first drop the cell using a tool in the Drop tool box .

Verifying Linkages
The Cell Link dialog box is used to link a cell library with an existing
database table by attaching database linkages to the library cells. You
can also use the dialog box to remove linkages from the library cells. For
more information about the Cell Link dialog box, see Cell Link Utility.
Verifying Linkages
When you delete an element that has an attached database linkage,
MicroStation automatically deletes the associated row from the
database table if Delete Linked Database Rows is on in the Database
dialog box. However, the opposite is not true. If you should delete
data from the database without removing linkage information from
an element, you create what is called an orphan linkage. Orphan
linkages are linkages without associated rows in the database.
A quick visual check of elements that have a database linkage can be

made by using a fence filter, a query that determines which elements
with linkages to rows in a table are selected for fence operations.
This procedure does not identify orphan linkages, but it does show
which elements do not have any attached linkages. For example, if
every desk in an office layout has a linkage, they will all highlight.
Those that are missing a linkage will not highlight.
For more comprehensive checking, consider Using the Database

Verification utility (see page 14-6) . It generates a listing of all
elements in the design file with database linkages of the type
selected and identifies orphan linkages.
To visually check for database linkages

1. In the Key-in Window, key in:DEFINE SEARCH SELECT
* FROM <table_name>
or
DS=SELECT * from <table_name>
This sets up a fence filter for all rows in the database
that have an mslink attachment. “Fence Filter: on”
displays in the status bar window.

Using the Database Verification utility
2. Use the Place Fence tool to fence the area of interest

(or the entire design).
3. In the Key-in window, key in: UC=hilite
All elements with database linkages will highlight.
The UC= key-in activates the sample user command (macro),

“hilite.ucm.” For more information about user commands,
see User Commands on page 9-3.
The Database Verification utility (“dbcheck.ma”) automates

detection and correction of orphan linkages.
To load the Database Verification utility

and open its dialog box
1. In the MDL dialog box (Utilities menu > MDL Applications),
select DBCHECK in the Available Applications list box.

2. Click the Load button.
Alternative method — To load the Database

Verification utility and open its dialog box
1. In the Key-in window, key in: MDL LOAD DBCHECK
To reopen the Database Verification Utility

dialog box once the utility is loaded
1. In the Key-in window, key in: DBCHECK
To find orphan linkages of a given type(s)

1. In the Linkage Types section of the Database Verification Utility
dialog box, select the linkage type(s) for analysis.
2. In the Options section, turn on Information Only. Always run the
utility with the Information Only option first before running
it with the other options that modify the design file.
3. To specify that the linkage information be written to the file
identified under Text File Output, turn on File.
or
To specify that the linkage information be displayed in the
Database Linkages dialog box, turn on List Box.

4. (Optional) — To change the output text file from the default,

“dbcheck.txt,” click the File button and specify the file to
create using the File Name dialog box. Then click the OK
button to return to the utility dialog box.
5. Click the Go button.

The utility generates the specified text file and/or opens the
Database Linkages dialog box. In either case the linkage
information is formatted as a table with one linkage per row, sorted
by type, then by entity number, and then by mslink key value.
Orphan linkages are identified by “Y” in the Orphan? column.
Database
Linkages
dialog box
Manipulating elements with orphan linkages
It is advisable to take one or more of the following corrective

actions after finding orphan linkages:
• Isolate elements with orphan linkages on a particular level.
• Remove the orphan linkages.
• Delete elements to which orphan linkages are attached.
The Database Linkages dialog box lets you individually manipulate

linkages. See Manipulating linkages individually on page 14-9.

To move all elements with orphan linkages of

a given type(s) to a single level
1. In the Options section of the Database Verification Utility dialog
box, turn on Move to New Level and, if desired, key in a value
in the field to replace the default destination level of 60.
Orphan elements will be moved to the level that
you have designated.
To remove all orphan linkages of a given type(s)

1. In the Options section of the Database Verification Utility
dialog box, turn on Detach Bad Linkage.
As each orphan linkage is removed, the element to which it
was attached is moved to the end of the design file.
To delete elements to which orphan linkages

of a given type(s) are attached
1. In the Options section of the Database Verification Utility
dialog box, turn on Delete Element.
Manipulating linkages individually
In addition to identifying orphan linkages, the Database Linkages

settings box can be used to individually manipulate linkages and
elements to which linkages are attached.
To change a linkage type

1. Run dbcheck with the list box option.
2. In the list box, select the linkage.

3. From the ID option menu, choose the desired type.

4. Click the Update Linkage button.
Changing DMRS linkage: You cannot change a DMRS linkage to

another linkage type nor change other linkage types to DMRS.
All other linkage types can be changed.
To change the entity number in a linkage

2. In the Entity field, key in the desired number.
To change the mslink key value in a linkage

2. In the Mslink field, key in the desired value.
When the Update Linkage button is clicked while an orphan

linkage is selected, the notation “Y” in the list box entry
for the linkage changes to “N/A.”
To delete an element with a linkage

1. In the list box, select any linkage to the element.
2. Click the Delete Element button.
All linkages to the element are dimmed in the list box to
indicate that the element is deleted.
To remove a linkage from an element

2. Click the Remove Linkage button.

Generating Reports
No matter what your application for the database interface, at
some point you will need to generate reports to communicate
information to others.
A report could be as simple as a parts list for a mechanical

component or as complex as a maintenance schedule for all
equipment in a selected area of a large facility that is still under
warranty and requires shutdown time for repair.
Whatever the application, you will find that a major strength

of the interface lies in its ability to combine the power of the
database query with graphical display for analysis, manipulation
and reports not otherwise possible.
In this chapter you will find procedures concerning generating reports

based on the database attributes of elements. In addition, this chapter
contains an overview of the report formatting and output capabilities
of the database products to which MicroStation provides an interface.
Report Tables
Database report output from MicroStation can either be plots of a
design with report information highlighted or report tables.
The Generate Report Table tool is used to generate a report table

for each table that has rows attached to elements contained in the
fence. A report table contains a row for each row of a particular
table attached to an element contained in the fence. Formatting

Generating Reports
Naming
and printing report tables requires report writer software that is

available with the relational database package being used (see
Report Formatting and Output on page 15-4).
Since a row is written to the report table for each occurrence of a

linked element, the table gives an accurate count of linkages that were
attached with Linkage Mode set to Duplicate. Recall that Duplicate
linkage mode lets the same row be attached to multiple elements.
Linkages that were attached with different linkage modes can even
be mixed in the same report table. Thus you may have hundreds of
identical items in a design, all with the same row attached, and still
generate a report table for inventory control or quantity-takeoffs.
Also note that linkages created with Linkage Mode set to

informational will not be reported.
To generate report tables

1. Make sure a report table name is specified in the MSCATALOG
table for each table that has rows attached to elements in the part
of the design you want to report on. See Naming on page 15-2.
2. (Optional) — To specify attribute-based criteria for reporting in
addition to the geographical criteria defined by the fence, define a
fence filter(s) (DS= ). See Fence Filters on page 15-3.
3. Place the fence so it contains the part of the design you want
to report on. Use the Place Fence tool.
4. Use the Generate Report Table tool.
The first three steps can be performed in any order.
Each time you generate report tables, any previously existing

report table with the same name is overwritten.
Naming
Before a report table can be generated, its name must be specified
in the reporttable column of the MSCATALOG table.

Generating Reports
Fence Filters
To check the report table names for all

tables listed in MSCATALOG
1. In the Command Window, key in: ACTIVE REPORT $
or
RS=$
The reporttable value for the first table is displayed
in the SQL Window.
2. Click the Next button to review the reporttable values
for successive tables.
To change a report table name specification

1. In the Command Window, key in: ACTIVE REPORT
<table_name>:<report_table_name>
or
RS=<table_name>:<report_table_name>
For example, to name a report table parts_report for a table
parts, key in: RS=parts:parts_report
The MSCATALOG dialog box can also be used to view and

change a report table name specification. From the MicroStation
command line use the key-in SET DATABASE.
Fence Filters
Fence filters are used in conjunction with the Generate Report Table
tool and also to generate reports in the form of plotted designs. A fence
filter specifies non-graphical criteria used to select elements for fence
operations. Report tables generated using fence filters contain only
rows for elements contained in the fence that meet the specified criteria.
This has the added advantage of allowing you to graphically
work with the selected elements.
The fencefilter row in MSCATALOG contains fence filter specifications.

Each table listed in MSCATALOG can have a unique fence filter.

Generating Reports
Report Formatting and Output
To discard previously defined fence filter

specifications and disable fence filter selection
1. In the Command Window, key in: DEFINE SEARCH none
or
DS=none
The fencefilter values are cleared from each row in MSCATALOG.
To define a fence filter and enable fence

filter selection
1. In the Command Window, key in: DEFINE SEARCH
<SQL_SELECT_statement>
or
DS=<SQL_SELECT_statement>
The specified SELECT statement is stored in the fencefilter
column of the row for the specified table in MSCATALOG.
Updating the fence filter row in MSCATALOG manually with a

SQL statement works under some circumstances, but it is strongly
discouraged. The DEFINE SEARCH or DS= commands both modify
this column, but they also turn the filtering operation on and off.
This command should only be executed by one user at a

time. Having multiple users execute this command can
produce unpredictable results.
You can use the sample user command, “hilite.bas,” to highlight

each element contained in the fence that meets the filter criteria.
Then you can use the Change Element Attributes tool, with Use
Fence on, to change the level, color, line style, or line weight of the
highlighted elements. These changes can be reflected in a plot to
dramatize an analysis. (For information about activating user
commands, see User Commands on page 9-3.)
Report Formatting and Output

A report table generated from within MicroStation can be formatted for
output as a report using a database report writing program. Following

Generating Reports
Oracle
is a brief discussion of the report writing programs available for the

database products to which MicroStation offers interfaces.
Oracle
Oracle supports report writing both from within the SQL*Plus
interface and with a sophisticated report writing package,
SQL*ReportWriter. SQL*Plus supports most report writing
functions. It allows you to control column layout, page size, add
headers and footers, and control breaks for subtotals. You can
also join tables and create summary reports.
SQL*ReportWriter lets you create single and multi-query

reports using a number of complex reporting formats. It uses
a fill-in-the-forms approach so no programming is required.
However, its breadth of features may intimidate users with
less sophisticated reporting requirements.

Generating Reports
Oracle

Database Application
Software
MicroStation Development Language (MDL) applications can
be used to extend the database interface and adapt it for more
specific uses. Like MDL applications that extend MicroStation
functionality outside the database interface, MDL database
applications can be acquired “off the shelf” from software publishers
or they can be developed using MDE (MicroStation Development
Environment) tools supplied with MicroStation.
In this chapter you will find some examples of types of commercially

available MDL database applications.
Existing Database Application Software

Following is a list of examples of types of commercially available
MDL database applications to help you understand how applications
can be used to extend the database interface:
• Architectural applications for automatically generating quantity
takeoffs, schedules, project file listings, and area takeoffs.
• Applications for associating spatial and other attributes to
plotted coordinate geometry data in site plans.
• Applications for visualizing work space utilization.
• Applications for converting geographic data between
coordinate systems.
• Applications that allow direct modification of database
rows using dialog boxes.
• Mechanical design applications for automatically generating parts
lists and position numbers and extracting details from drawings.
For general information about acquiring and using MDL applications,

see MDL Applications on page 10-1.

Database Application Software
Developing MDL Database Applications
Developing MDL Database Applications

MDL (MicroStation Development Language) is the primary
programming interface for developing applications for MicroStation.
MDL is a complete implementation of the ANSI-standard
C programming language. MDL allows developers access to
all MicroStation graphic and database interface functions,
as well as complete control over the graphical user interface
using menus and dialog boxes.
Although the fundamentals of MDL programming are beyond
the scope of this guide, the sample application, “gis.ma,” should
give you an appreciation of the potential of MDL for developing
custom database applications. For general information about
MDL and developing MDL applications, see The MDL Alternative
in the MicroStation BASIC Guide.

Index
A Windows Explorer . . . . . . . . . . . . . . . . 6–112
AC= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 Archive dialog box
Action Strings . . . . . . . . . . . . . . . . . . . . . . . 4–41 and digital signatures . . . . . . . . . . . . . 6–107
Action Type . . . . . . . . . . . . . . . . . . . . . . . . . 4–48 to verify file . . . . . . . . . . . . . . . . . . . . . . 6–110
ACTIVE CELL . . . . . . . . . . . . . . . . . . . . . . . 6–6 archive files
ACTIVE DATABASE . . . . . . . . . . . . . . . . . 12–7 updating . . . . . . . . . . . . . . . . . . . . . . . . 6–110
Active Entity Assign
attach to element . . . . . . . . . . . . . . . . . 13–39 Equation . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
define database row as . . . . . . . . . . . . . 13–39 Variable to Dimensional Constraint . . . 6–26
edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–41 Attach
linkage mode and . . . . . . . . . . . . . . . . . 13–41 color table . . . . . . . . . . . . . . . . . . . . . . . . 6–61
ACTIVE ENTITY . . . . . . . . . . . . . . . . . . . 13–40 database linkage to element . . . . . . . . 13–39
ACTIVE INDEX . . . . . . . . . . . . . . . . . . . . . . 9–4 Element to Point . . . . . . . . . . . . . . . . . . . 6–30
Active Point Pen Element to Point . . . . . . . . . . . . . . . 6–31
settings group component . . . . . . . . . . . 6–89 redline file . . . . . . . . . . . . . . . . . . . . . . . . 5–83
ACTIVE REVIEW . . . . . . . . . . . . . . . . . . . 14–1 row to element . . . . . . . . . . . . . . . . . . . 13–39
ACTIVE TAB . . . . . . . . . . . . . . . . . . . . . . . 5–81 Attach Active Entity . . . . . . . . . . . . . . . . 13–39
AE= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–40 Attach Active Entity to Fence Contents . 13–39
Algebraic expression . . . . . . . . . . . . . . . . . 6–12 ATTACH ARC . . . . . . . . . . . . . . . . . . . . . . . 6–29
Align Element with Point and Line . . . . . 6–30 ATTACH CIRCLE . . . . . . . . . . . . . . . . . . . 6–30
AM= . . . . . . . . . . . . . . . . . . . . 4–27, 4–31, 4–33 Attach Displayable Attributes . . . . . . . . . 14–3
Animation Sequence . . . . . . . . . . . . . . . . . 5–66 Attach Element Tool Box . . . . . . . . . . . . . . 6–27
Application Software Align Element with Point and Line . . . . 6–30
database . . . . . . . . . . . . . . . . . . . . . . . . . 16–1 Attach Element to Point . . . . . . . . . . . . 6–30
key-in script . . . . . . . . . . . . . . . . . . . . . . . 9–1 Attach Pen Element to Point . . . . . . . . . 6–31
macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1 Construct Attached Arc . . . . . . . . . . . . . 6–29
MDL Application . . . . . . . . . . . . . . . . . . 10–1 Construct Attached Ellipse or Circle . . . 6–29
user command . . . . . . . . . . . . . . . . . . . . . . 9–3 Construct Attached Line String or
applications Shape . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28
editing view objects in other . . . . . . . . . 5–69 ATTACH LOCATION . . . . . . . . . . . . . . . . . 6–30
sending views to other . . . . . . . . . . . . . . 5–67 ATTACH LSTRING . . . . . . . . . . . . . . . . . . 6–29
Arc ATTACH MENU . . . . . . . . . . . . . . . 4–31, 4–33
construct attached . . . . . . . . . . . . . . . . . 6–29 ATTACH PEN . . . . . . . . . . . . . . . . . . . . . . 6–32
Architecture ATTACH TRANSFORM . . . . . . . . . . . . . . 6–31
sample workspace . . . . . . . . . . . . . . . . . . . 2–2 ATTACH WEBTAG . . . . . . . . . . . . . . . . . . . 7–5
Archive Audio Notes . . . . . . . . . . . . . . . . . . . . . . . . 5–65
bundling module data files . . . . . . . . . . 6–97 AutoCAD
file selection . . . . . . . . . . . . . . . . . . . . . . 6–98 transition from . . . . . . . . . . . . . . . . . . . . . 2–9
overview . . . . . . . . . . . . . . . . . . . . . . . . . 6–97 translating files from . . . . . . . . . . . . . . . 5–10
resource classes . . . . . . . . . . . . . . . . . . 6–113 AutoSave in container application, and closing
restoration . . . . . . . . . . . . . . . . . . . . . . . . 6–99 MicroStation . . . . . . . . . . . . . . . . . . . . . . 5–71
MicroStation/J Administrator’s Guide i–1

Index
B version support . . . . . . . . . . . . . . . . . . . . . 5–9
Bitmapped File . . . . . . . . . . . . . . . . . . . . . . 5–59 Chamfer
Bitmaps Constrained Geometry . . . . . . . . . . . . . . 6–51
in 3D files . . . . . . . . . . . . . . . . . . . . . . . . 5–63 Circle
bookmarks constrain center . . . . . . . . . . . . . . . . . . . 6–38
for URLs . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8 constrain point to lie at center . . . . . . . . 6–40
Break constrain two to be concentric . . . . . . . . 6–40
Constrained Geometry . . . . . . . . . . . . . . 6–48 construct attached . . . . . . . . . . . . . . . . . 6–29
Browser Civil Engineering
connect to . . . . . . . . . . . . . . . . . . . . . . . . . 7–5 sample workspace . . . . . . . . . . . . . . . . . . 2–10
BROWSER CONNECT . . . . . . . . . . . . . . . . 7–6 CLIPBOARD VIEWCOPY . . . . . . . . . . . . . 5–68
BROWSER REFAGENT . . . . . . . . . . . . . . . 7–7 closing
MicroStation, container AutoSave and . 5–71
C Color
CALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–29 duplicate . . . . . . . . . . . . . . . . . . . . . . . . . 6–64
CAPTURE FOCUS . . . . . . . . . . . . . 5–56, 5–59 interpolation . . . . . . . . . . . . . . . . . . . . . . 6–63
CAPTURE RECTANGLE . . . . . . . . 5–56, 5–58 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–64
CAPTURE SCREEN . . . .5–56 thru 5–57, 5–59 table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–62
CAPTURE VIEW CONTENTS . . . . 5–56, 5–58 Color Table . . . . . . . . . . . . . . . . . . . . . . . . . 6–61
CAPTURE VIEW WINDOW . . . . . . 5–56, 5–58 attach . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–61
Cell customize . . . . . . . . . . . . . . . . . . . . . . . . 6–62
derived . . . . . . . . . . . . . . . . . . . . . . . 6–8, 6–54 default . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96
menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34 Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–92 mslink . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
settings group component . . . . . . . . . . . 6–89 Command File
tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42 SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–27
Cell Library . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 Command Menu . . . . . . . . . . . . .4–29 thru 4–30
attach linkage to . . . . . . . . . . . . . . . . . . 13–43 action string . . . . . . . . . . . . . . . . . . . . . . 4–34
build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 action types . . . . . . . . . . . . . . . . . . . . . . . 4–48
detach linkage from header . . . . . . . . . . 14–4 attach (activate) . . . . . . . . . . . . . . . . . . . 4–31
directories . . . . . . . . . . . . . . . . . . . . . . . . 6–96 block . . . . . . . . . . . . . . . . . . . . . . . 4–29, 4–34
link to database table . . . . . . . . . . . . . . 13–43 cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
link with database . . . . . . . . . . . . . . . . 13–43 control information . . . . . . . . . . . . . . . . . 4–34
list . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6, 6–96 create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
multiple . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 deactivate . . . . . . . . . . . . . . . . . . . . . . . . 4–33
use of multiple . . . . . . . . . . . . . . . . . . . . . 6–6 design file . . . . . . . . . . . . . . . . . . . . . . . . 4–34
CGM Export graphical information . . . . . . . . . . . . . . . 4–34
interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–13 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39
version support . . . . . . . . . . . . . . . . . . . . . 5–9 sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33
CGM File Format . . . . . . . . . . . . . . . . . . . . . 5–1 Compound Line Style . . . . . . . . . . . . . . . . . 6–69
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1 create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–81
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1 delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–83
versions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–83
CGM Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3–7
interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–11 Configuration File
processing . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
i–2 MicroStation/J Administrator’s Guide

Index
project . . . . . . . . . . . . . . . . . . . 1–1, 3–5, 6–96 MS_RFDIR . . . . . . . . . . . . . . . . . . . . . . . 6–96
user . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1, 3–5 MS_SEEDFILES . . . . . . . . . . . . . . . . . . 6–96
Configuration Variable Files MS_SETTINGS . . . . . . . . . . . . . . . . . . . 6–96
debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–45 MS_SETTINGSDIR . . . . . . . . . . . . . . . . 6–96
syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–40 MS_SHADOWMAP . . . . . . . . . . . . . . . . 6–96
Configuration Variables . . . . . . . . . . . . 3–1, 5–7 MS_SHEETSEED . . . . . . . . . . . . . . . . . 6–96
application-level . . . . . . . . . . . . . . . . . . . . 3–3 MS_SYMBRSRC . . . . . . . . . . . . . . . . . . . 6–96
define . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7 MS_TAGOUTPUT . . . . . . . . . . . . . . . . . 6–96
definition . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 MS_TAGTEMPLATES . . . . . . . . . . . . . . 6–96
directory . . . . . . . . . . . . . . . . . . . . . . 3–4, 3–9 MS_TUTLIB . . . . . . . . . . . . . . . . . . . . . . 6–96
edit . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7, 3–11 MS_UCM . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
Embed Reference Files . . . . . . . . . . . . . . 5–71 MS_USEEXTERNALBROWSER . . . . . 3–12
expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7 MS_WEBBOOKMARKS . . . . . . . . . . . . 3–12
filename . . . . . . . . . . . . . . . . . . . . . 3–4, 3–10 MS_WEBCACHEDIR . . . . . . . . . . . . . . 3–12
keyword . . . . . . . . . . . . . . . . . . . . . . 3–4, 3–11 MS_WEBDOWNLOADDIR . . . . . . . . . . 3–12
levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3 MS_WEBHISTORYLOG . . . . . . . . . . . . 3–12
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–7 MS_WEBKIOSKMODE . . . . . . . . . . . . . 3–12
MS_BATCHPLT_SPECS . . . . . . . . . . . . 3–12 MS_WEBPAGEHOME . . . . . . . . . . . . . . 3–12
MS_BUMP . . . . . . . . . . . . . . . . . . . . . . . 6–96 MS_WEBTYPESFILE . . . . . . . . . . . . . . 3–12
MS_CELL . . . . . . . . . . . . . . . . . . . . . . . . 6–96 path . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4, 3–8
MS_CELLLIST . . . . . . . . . . . . . . . . 6–6, 6–96 processing . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
MS_CELLSEED . . . . . . . . . . . . . . . . . . . 6–96 project-level . . . . . . . . . . . . . . . . . . . 3–3, 3–39
MS_DEF . . . . . . . . . . . . . . . . . . . . . . . . . 6–96 site-level . . . . . . . . . . . . . . . . . . . . . 3–3, 3–39
MS_DEFCTBL . . . . . . . . . . . . . . . 6–61, 6–96 system-level . . . . . . . . . . . . . . . . . . 3–3, 3–39
MS_DESIGNSEED . . . . . . . . . . . . . . . . 6–96 table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38
MS_ENHANCEDPRECISION . . . . . . . 3–12 types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
MS_FKEYMNU . . . . . . . . . . . . . . . . . . . 6–96 user-level . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
MS_GLOSSARY . . . . . . . . . . . . . . . . . . . 6–96 Connect
MS_GRAPHICSACCELERATOR . . . . . 3–12 browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5
MS_IGESINSET . . . . . . . . . . . . . . . . . . . . 5–7 Constrain
MS_IMAGE . . . . . . . . . . . . . . . . . . . . . . . 6–96 Elements . . . . . . . . . . . . . . . . . . . . . . . . . 6–33
MS_KEYPAIRLIST . . . . . . . . . . 3–12, 6–107 Point at Intersection . . . . . . . . . . . . . . . . 6–39
MS_LEVELNAMES . . . . . . . . . . . . . . . . 6–96 Point On Construction . . . . . . . . . . . . . . 6–38
MS_LIGHTING . . . . . . . . . . . . . . . . . . . 3–12 Two Points to be Coincident . . . . . . . . . . 6–40
MS_LINKTYPE . . . . . . . . . . . . . . . . . . 12–12 CONSTRAIN CONCENTRIC . . . . . . . . . . 6–40
MS_MATERIAL . . . . . . . . . . . . . . . . . . . 6–96 CONSTRAIN CONSTANT . . . . . . . . . . . . 6–38
MS_MENU . . . . . . . . . . . . . . . . . . . . . . . 6–96 CONSTRAIN DIMENSION . . . . . . . . . . . 6–25
MS_OLECNTR_CNFIG_DOESBLACK CONSTRAIN EQUATION . . . . . . . . . . . . . 6–26
ANDWHITEINVERT . . . . . . . . . . . . . 5–72 CONSTRAIN INTERSECTION . . . . . . . . 6–40
MS_OLECNTR_CONFIG_ CONSTRAIN LOCATION . . . . . . . . . . . . . 6–41
ADDWHITEBACKGROUND . . . . . . . 5–72 CONSTRAIN MATCH . . . . . . . . . . . . . . . . 6–42
MS_OLECNTR_CONFIG_ CONSTRAIN POINTON . . . . . . . . . . . . . . 6–39
CREATEOBJECTSASCELLS . . . . . . 5–72 CONSTRAIN VARIABLE . . . . . . . . . . . . . 6–26
MS_OLECNTR_FONTMAP_ . . . . . . . . . 5–72 Constraints
MS_OLESERVE_EMBED_REFFILES . 5–71 display where needed for a profile . . . . . 6–43
MS_PATTERN . . . . . . . . . . . . . . . . . . . . 6–96 rules for applying . . . . . . . . . . . . . . . . . . 6–17

Index
Construct log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8
Attached Arc . . . . . . . . . . . . . . . . . . . . . . 6–29 measurements . . . . . . . . . . . . . . . . . . . . . 5–6
Attached Ellipse or Circle . . . . . . . . . . . 6–29 settings file . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Attached Line String or Shape . . . . . . . 6–28 units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
Containers Database
editing embedded view object from . . . . 5–69 query . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Convert relational . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
CGM file to design file . . . . . . . . . . . . . . . 5–3 Database Attributes
design file to CGM format . . . . . . . . . . . . 5–3 display in design . . . . . . . . . . . . . 14–2, 13–34
design file to IGES format . . . . . . . . . . . . 5–3 displayable types . . . . . . . . . . . . . . . . . . 14–2
IGES file to design file . . . . . . . . . . . . . . . 5–3 load into text node . . . . . . . . . . . . . . . . . 14–3
Convert Element load into text nodes in fence contents . . 14–3
to Profile . . . . . . . . . . . . . . . . . . . . . . . . . 6–22 review . . . . . . . . . . . . . . . . . . . . . . . . . . 13–33
CONVERT PROFILE . . . . . . . . . . . . . . . . 6–23 review selection criteria . . . . . . . . . . . . . 14–1
Converting Database forms
custom V5 palettes to a tool box . . . . . . . 4–7 operations . . . . . . . . . . . . . . . . . . . . . . . 13–14
Copy Database Forms . . . . . . . . . . . . . . . . . . . . 13–14
from application . . . . . . . . . . . . . . . . . . . 5–64 Database Linkage
text elements . . . . . . . . . . . . . . . . . . . . . 5–62 attach to cell library header . . . . . . . . . 13–43
Create attach to element . . . . . . . . . . . . . . . . . 13–39
cell library . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 change type of . . . . . . . . . . . . . . . . . . . . . 14–9
CREATE SYMBOL . . . . . . . . . . . . . . . . . . 6–80 create . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–39
Cursor Button Menu . . . .4–29 thru 4–30, 4–35 detach . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4
action string . . . . . . . . . . . . . . . . . . . . . . 4–34 detach from fence contents . . . . . . . . . . 14–4
action types . . . . . . . . . . . . . . . . . . . . . . . 4–48 entity number . . . . . . . . . . . . . . . . . . . . . 14–9
activate . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31 establish . . . . . . . . . . . . . . . . . . . . . . . . 13–39
cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34 orphan . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4
control information . . . . . . . . . . . . . . . . . 4–34 types . . . . . . . . . . . . . . . . . . . . . . 14–9, 12–12
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35 verify . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4
deactivate . . . . . . . . . . . . . . . . . . . . . . . . 4–33 Database Products
design file . . . . . . . . . . . . . . . . . . . . . . . . 4–34 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33 RIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
Custom Line Style Database Server . . . . . . . . . . . . . . . . . . . . . 11–5
component . . . . . . . . . . . . . . . . . . . . . . . . 6–67 model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
compound . . . . . . . . . . . . . . . . . . . . . . . . 6–65 DB= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
define . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–69 DB2
definition . . . . . . . . . . . . . . . . . . . . . . . . . 6–65 interface through RIS . . . . . . . . . . . . . . 11–11
library . . . . . . . . . . . . . . . . . . . . . . 6–65, 6–96 DD Design tool frame . . . . . . . . . . . . . . . . 6–15
Customize dialog box DDE Links . . . . . . . . . . . . . . . . . . . . . . . . . 5–63
Convert Palettes . . . . . . . . . . . . . . . . . . . . 4–1 end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
establish . . . . . . . . . . . . . . . . . . . . . . . . . 5–80
D Define Active Entity Graphically . . . . . . 13–39
Data Exchange . . . . . . . . . . . . . . . . . . . . . . . 5–1 DEFINE SEARCH . . . . . . . . . . . . . . . . . . . 14–5
export . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–12 Degrees of Freedom . . . . . . . . . . . . . . 6–8, 6–11
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9 Design File
convert other format to . . . . . . . . . . . . . . 5–9

Index
menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34 construction . . . . . . . . . . . . . . . . . . . . . . . 6–8
open other format as . . . . . . . . . . . . . . . . 5–9 degrees of freedom . . . . . . . . . . . . . 6–8, 6–11
seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 dialog box . . . . . . . . . . . . . . . . . . . . . . . . 6–54
design files dimensional constraint . . . . . . . . . . . . . . . 6–9
editing linked object in . . . . . . . . . . . . . . 5–72 equation syntax . . . . . . . . . . . . . . . . . . . 6–12
editing linked or embedded objects in . . 5–75 geometric constraint . . . . . . . . . . . . . . . . . 6–9
embedded objects in . . . . . . . . . . . . . . . . 5–72 location constraint . . . . . . . . . . . . . . . . . . 6–9
linking objects into . . . . . . . . . . . . . . . . . 5–72 numerical constant in equation . . . . . . . 6–25
Detach redundant constraint . . . . . . . . . . . . . . . . 6–8
redline file . . . . . . . . . . . . . . . . . . . . . . . . 5–84 solve constraints . . . . . . . . . . . . . . . . . . . . 6–9
Detach Database Linkage . . . . . . . . . . . . . 14–4 variable names in equation . . . . . . . . . . 6–25
Detach Database Linkage from Fence Dimension-driven Profile
Contents . . . . . . . . . . . . . . . . . . . . . . . . . 14–4 convert element to . . . . . . . . . . . . . . . . . 6–22
Dialog Box display where constraints are needed . . 6–43
capture . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–45
DIALOG TOOLBOX DDDCONSTRAINT 6–33 sketch . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
DIALOG TOOLBOX DDDDRAW . . . . . . . 6–17 Dimensional Constraint
DIALOG TOOLBOX DDDMODEL . . . . . . 6–43 assign variable to . . . . . . . . . . . . . . . . . . 6–26
DIALOG TOOLBOX DDDMODIFY . . . . . 6–48 convert dimension to . . . . . . . . . . . . . . . 6–24
DIALOG TOOLBOX DDDPARM . . . . . . . 6–24 DS= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5
DIALOG TOOLBOX DDDTOOLS . . . . . . 6–16 DWG File Format
DIALOG TOOLBOX REDLINE . . . . . . . . 5–83 versions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
DIALOG WEBTOOLS . . . . . . . . . . . . . . . . . 7–2 DWG/DXF Export
digital signatures interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–13
adding to document . . . . . . . . . . . . . . . 6–107 version support . . . . . . . . . . . . . . . . . . . . . 5–9
algorithms for . . . . . . . . . . . . . . . . . . . . 6–112 DWG/DXF Import
key pairs . . . . . . . . . . . . . . . . . . . . . . . . 6–107 interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–11
overview . . . . . . . . . . . . . . . . . . . . . . . . 6–106 version support . . . . . . . . . . . . . . . . . . . . . 5–9
typical uses . . . . . . . . . . . . . . . . . . . . . . 6–106 DXF File Format
verifying . . . . . . . . . . . . . . . . . . . . . . . . 6–110 versions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
Digitizing Tablet Dynamic Data Exchange Links . . . . . . . . . 5–63
menu . . . . . . . . . . . . . . . . . . . .4–29 thru 4–30
Dimension E
convert to constraint . . . . . . . . . . . . . . . 6–24 Edit
style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–93 Active Entity . . . . . . . . . . . . . . . . . . . . . 13–41
Dimension-driven Cell . . . . . . . . . . . . . . . . . 6–8 EDIT AE . . . . . . . . . . . . . . . . . . . . . . . . . . 13–41
derive for placement . . . . . . . . . . . . . . . . 6–54 Edit menu
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–54 Paste Special . . . . . . . . . . . . . . . . . . . . . . 5–74
place as derived . . . . . . . . . . . . . . . . . . . 6–54 Edit Menu
underlying constraint . . . . . . . . . . . . . . . 6–54 Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
Dimension-driven Design Cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
algebraic constraint . . . . . . . . . . . . . . . . . 6–9 Paste . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–64
algebraic expression in equation . . . . . . 6–12 Paste Special . . . . . . . . . . . . . . . . . 5–64, 5–73
arithmetic operators in equation . . . . . . 6–25 editing
constraint . . . . . . . . . . . . . . . . . . . . . . . . . 6–8 linked or embedded objects . . . . . . . . . . 5–75
constraint symbology . . . . . . . . . . . . . . . 6–11

Index
Element sharing among projects . . . . . . . . . . . . . . 6–4
convert to profile . . . . . . . . . . . . . . . . . . . 6–22 UCM index . . . . . . . . . . . . . . . . . . . . . . . . 9–5
tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1 user preferences . . . . . . . . . . . . . . . . . . . . 1–1
Ellipse File Menu
constrain center . . . . . . . . . . . . . . . . . . . 6–38 Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5
construct attached . . . . . . . . . . . . . . . . . 6–29 Save Settings . . . . . . . . . . . . . . . . . . . . . . 6–6
embedded objects . . . . . . . . . . . . . . . . . . . . 5–67 files
editing . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–75 digital signatures for . . . . . . . . . . . . . . 6–107
in design files . . . . . . . . . . . . . . . . . . . . . 5–72 verifying digital signature . . . . . . . . . . 6–110
updating . . . . . . . . . . . . . . . . . . . . . . . . . 5–75 Fillet
Engineering Links . . . . . . . . . . . . . . . . . . . . 7–1 Constrained Geometry . . . . . . . . . . . . . . 6–49
attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3 FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–40
follow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5 Fix Point at Location . . . . . . . . . . . . . . . . . 6–41
show . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2 Fixed Point, move . . . . . . . . . . . . . . . . . . . . 6–17
Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4 FOLLOW WEBTAG . . . . . . . . . . . . . . . . . . . 7–5
Entity number . . . . . . . . . . . . . . . . . . . . . 13–32 font conversion . . . . . . . . . . . . . . . . . . . . . . 5–21
Environment Variables Font Library
MS_CONFIG . . . . . . . . . . . . . . . . . . . . . 3–38 default open . . . . . . . . . . . . . . . . . . . . . . 6–96
operating system . . . . . . . . . . . . . . . . . . 3–38 fonts
Equate Parameters or Constructions . . . . 6–41 MicroStation support of TrueType . . . . . 5–72
Equation syntax . . . . . . . . . . . . . . . . . . . . . 6–12 Form Dialogs . . . . . . . . . . . . . . . . . . . . . . 13–18
Equation, assign . . . . . . . . . . . . . . . . . . . . . 6–25 adding items to . . . . . . . . . . . . . . . . . . . 13–20
Evaluate Constraints Tool Box . . . . . . . . . 6–42 deleting items from . . . . . . . . . . . . . . . 13–20
Describe Selected Construction or moving items on . . . . . . . . . . . . . . . . . . 13–18
Constraint . . . . . . . . . . . . . . . . . . . . . . 6–46 opening . . . . . . . . . . . . . . . . . . . . . . . . . 13–18
Modify and Re-solve Constraints . . . . . . 6–45 resizing items in . . . . . . . . . . . . . . . . . . 13–18
Re-solve Constraints . . . . . . . . . . . . . . . 6–43 saving . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21
Export Function Keys . . . . . . . . . . . . . . . . . . . . . . 4–27
CGM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3 assignment . . . . . . . . . . . . . . . . . . . . . . . 4–27
design file . . . . . . . . . . . . . . . . . . . . . . . . 5–12 default menu . . . . . . . . . . . . . . . . . . . . . . 6–96
IGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3 menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
image file . . . . . . . . . . . . . . . . . . . . . . . . . 5–59 menu action types . . . . . . . . . . . . . . . . . . 4–48
modifiers . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
F
Fence Contents G
detach rows from . . . . . . . . . . . . . . . . . . 14–4 Geometric Constraints Tool Box . . . . . . . . 6–32
load attributes in text nodes in . . . . . . . 14–3 Constrain Elements . . . . . . . . . . . . . . . . 6–33
Fence Filter Constrain Point at Intersection . . . . . . . 6–39
check linkages with . . . . . . . . . . . . . . . . 14–5 Constrain Point On Construction . . . . . 6–38
generate report table with . . . . . . . . . . . 15–3 Constrain Two Points to be Coincident . 6–40
FI= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–40 Equate Parameters or Constructions . . 6–41
File Fix Point at Location . . . . . . . . . . . . . . . 6–41
configuration . . . . . . . . . . . . . . . . . . . . . . . 1–1 Make Construction or Parameter
duplication . . . . . . . . . . . . . . . . . . . . . . . . 6–4 Invariant . . . . . . . . . . . . . . . . . . . . . . . 6–38
level structure . . . . . . . . . . . . . . . . . . . . . 6–55 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96

Index
Group export . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
settings . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84 import . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
GroupBy Clause . . . . . . . . . . . . . . . . . . . . . 13–7 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–62
save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
I supported formats . . . . . . . . . . . . . . . . . 5–59
IGES Export Import
alternate entities . . . . . . . . . . . . . . . . . . 5–28 CGM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
CALS-compliance . . . . . . . . . . . . . . . . . . 5–29 IGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
cell conversion . . . . . . . . . . . . . . . . . . . . . 5–20 image file . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
element conversion . . . . . . . . . . . . . . . . . 5–38 text file . . . . . . . . . . . . . . . . . . . . . . . . . . 5–81
error messages . . . . . . . . . . . . . . . . . . . . 5–39 import/export
exclude IGES entities . . . . . . . . . . . . . . . 5–27 JAMA-IS IGES translator . . . . . . . . . . . 5–14
interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–13 Importing
version support . . . . . . . . . . . . . . . . . . . . . 5–9 V5 menus . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
warning messages . . . . . . . . . . . . . . . . . 5–39 V5 palettes . . . . . . . . . . . . . . . . . . . . . . . . 4–5
IGES File Format . . . . . . . . . . . . . . . . . . . . . 5–1 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
CALS-compliant . . . . . . . . . . . . . . . . . . . 5–29 INFORMIX . . . . . . . . . . . . . . . . . . . . . . . . . 11–5
check conformance of file to . . . . . . . . . . 5–47 interface through RIS . . . . . . . . . . . . . . 11–11
directory entry section . . . . . . . . . . . . . . 5–17 Input Focus . . . . . . . . . . . . . . . . . . . . . . . . . 5–59
entities . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15 Interfaces
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1 in Workspaces . . . . . . . . . . . . . . . . . . . . . . 1–5
global data section . . . . . . . . . . . . . . . . . 5–17
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1 J
parameter data section . . . . . . . . . . . . . 5–17 JAMA-IS IGES translator . . . . . . . . . . . . . 5–14
reference sources . . . . . . . . . . . . . . . . . . 5–47 Join
start section . . . . . . . . . . . . . . . . . . . . . . 5–16 table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
terminate section . . . . . . . . . . . . . . . . . . 5–18
versions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9 K
IGES Import key pairs
entity conversion . . . . . . . . . . . . . . . . . . 5–33 for digital signatures . . . . . . . . . . . . . . 6–107
error messages . . . . . . . . . . . . . . . . . . . . 5–39 Key-in
font conversion . . . . . . . . . . . . . . . . . . . . 5–22 receive from other application . . . . . . . . 5–80
interactive . . . . . . . . . . . . . . . . . . . . . . . . 5–11 script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
level mapping . . . . . . . . . . . . . . . . . . . . . 5–24 Keyboard
line font pattern conversion . . . . . . . . . . 5–23 function key assignments . . . . . . . . . . . 4–27
model file and sheet files . . . . . . . . . . . . 5–26
subfigure conversion . . . . . . . . . . . . . . . 5–20 L
translation units . . . . . . . . . . . . . . . . . . . 5–24
Level
unit conversion . . . . . . . . . . . . . . . . . . . . 5–24
assign to group . . . . . . . . . . . . . . . . . . . . 6–58
version support . . . . . . . . . . . . . . . . . . . . . 5–9
build group . . . . . . . . . . . . . . . . . . . . . . . 6–55
view visibility . . . . . . . . . . . . . . . . . . . . . 5–26
remove from group . . . . . . . . . . . . . . . . . 6–60
warning messages . . . . . . . . . . . . . . . . . 5–39
save group structure . . . . . . . . . . . . . . . 6–60
IGES, Japanese subset . . . . . . . . . . . . . . . 5–14
structure . . . . . . . . . . . . . . . . . . . . 6–55, 6–96
Image File
Level Names . . . . . . . . . . . . . . . . . . . . . . . . 6–56
color depth . . . . . . . . . . . . . . . . . . . . . . . 5–62
Library

Index
cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 attach (activate) . . . . . . . . . . . . . . . . . . . 4–31
font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 block . . . . . . . . . . . . . . . . . . . . . . . 4–29, 4–34
line style . . . . . . . . . . . . . . . . . . . . 6–65, 6–96 cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34
Line String control information . . . . . . . . . . . . . . . . . 4–34
construct attached . . . . . . . . . . . . . . . . . 6–28 create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
Line Style deactivate . . . . . . . . . . . . . . . . . . . . . . . . 4–33
compound (custom) . . . . . . . . . . . . . . . . . 6–69 design file . . . . . . . . . . . . . . . . . . . . . . . . 4–34
line style definitions graphical information . . . . . . . . . . . . . . . 4–34
copying . . . . . . . . . . . . . . . . . . . . . . . . . . 6–65 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
Line Style Editor dialog box . . . . . . . . . . . 6–65 sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33
Linkage Mode . . . . . . . . . . . . . . . . . . . . . . 13–41 MDL
Duplicate . . . . . . . . . . . . . . . . . . . . . . . . 13–42 programming database applications
effect on Active Entity . . . . . . . . . . . . . 13–41 with . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2
Information . . . . . . . . . . . . . . . . . . . . . . 13–42 MDL Application . . . . . . . . . . . . . . . . . . . . 10–1
New . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–42 automatic loading of . . . . . . . . . . . . . . . . 10–4
linked objects . . . . . . . . . . . . . . . . . . . . . . . 5–67 detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
editing . . . . . . . . . . . . . . . . . . . . . . 5–72, 5–75 load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2
in design files . . . . . . . . . . . . . . . . . . . . . 5–72 unload . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
updating . . . . . . . . . . . . . . . . . . . . . . . . . 5–75 MDL LOAD . . . . . . . . . . . . . . . . . . . . . . . . 10–2
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–63 MDL LOAD DDCELL . . . . . . . . . . . . . . . . 6–54
attach engineering . . . . . . . . . . . . . . . . . . 7–3 MDL LOAD MERGE . . . . . . . . . . . . . . . . . 10–2
follow engineering . . . . . . . . . . . . . . . . . . 7–5 MDL LOAD OLESERVE . . . . . . . . . . . . . . 5–68
show engineering . . . . . . . . . . . . . . . . . . . 7–2 MDL UNLOAD . . . . . . . . . . . . . . . . . . . . . 10–3
Links dialog box Mechanical Drafting
manual or automatic updates . . . . . . . . 5–75 sample workspace . . . . . . . . . . . . . . . . . . 2–23
Load Displayable Attributes . . . . . . . . . . . 14–3 Menu
Load Displayable Attributes to Fence capture . . . . . . . . . . . . . . . . . . . . . . . . . . 5–58
Contents . . . . . . . . . . . . . . . . . . . . . . . . . 14–3 command . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8 cursor button . . . . . . . . . . . . . . . . . . . . . 4–30
Lot Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3 design file . . . . . . . . . . . . . . . . . . . . . . . . 4–34
digitizing tablet . . . . . . . . . . . . . . . . . . . 4–29
M function key assignments . . . . . . . . . . . 4–27
Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1 matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2 name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2 paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
Make Construction or Parameter Menu Bar
Invariant . . . . . . . . . . . . . . . . . . . . . . . . . 6–38 delete menu from . . . . . . . . . . . . . . . . . . 4–17
Manage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84 insert menu in . . . . . . . . . . . . . . . . . . . . 4–21
Mapping move menu in . . . . . . . . . . . . . . . . . . . . . 4–17
sample workspace . . . . . . . . . . . . . . . . . . 2–15 Menu Customization
Material modify menu item . . . . . . . . . . . . . . . . . . 4–19
palette . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96 Menu Item
Matrix Menu . . . . . . . . . . . . . . .4–29 thru 4–30 accelerator . . . . . . . . . . . . . . . . . . . 4–19, 4–22
action string . . . . . . . . . . . . . . . . . . . . . . 4–34 associated key-in . . . . . . . . . . . . . 4–19, 4–22
action types . . . . . . . . . . . . . . . . . . . . . . . 4–48 change position in menu . . . . . . . . . . . . 4–17
delete from menu . . . . . . . . . . . . . . . . . . 4–17

Index
insert in menu . . . . . . . . . . . . . . . . . . . . 4–21 N
label (name) . . . . . . . . . . . . . . . . . . . . . . 4–18 New
mnemonic access character . . . . . 4–19, 4–22 project . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19 workspace . . . . . . . . . . . . . . . . . . . . 1–8, 1–11
MODEL EDIT_DIMENSION . . . . . . . . . . 6–54
MODEL UPDATE . . . . . . . . . . . . . . . . . . . 6–45 O
Modify OLE containers . . . . . . . . . . . . . . . . . . . . . 5–67
and Re-solve Constraints . . . . . . . . . . . . 6–45 MicroStation as . . . . . . . . . . . . . . . . . . . . 5–72
dimension-driven profile . . . . . . . . . . . . 6–45 OLE2 Server
Value of Dimension or Variable . . . . . . . 6–53 loading . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–68
Modify Constraint Tool Box . . . . . . . . . . . . 6–47 OLESERVE UPDATE . . . . . . . . . . . . . . . . 5–71
Break Constrained Geometry . . . . . . . . 6–48 OLESERVE VIEWCOPY . . . . . . . . . . . . . . 5–68
Chamfer Constrained Geometry . . . . . . 6–51 Open Archive File dialog box . . . . . . . . . . 6–110
Fillet Constrained Geometry . . . . . . . . . 6–49 Oracle . . . . . . . . . . . . . . . . . . . . . . . . 11–5, 11–7
Modify Value of Dimension or Variable . 6–53 interface through RIS . . . . . . . . . . . . . . 11–11
Trim Constrained Geometry . . . . . . . . . 6–49 product bundles . . . . . . . . . . . . . . . . . . . 11–7
MODIFY DIMENSION . . . . . . . . . . . . . . . 6–54 product descriptions . . . . . . . . . . . . . . . . 11–8
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6 reports with . . . . . . . . . . . . . . . . . . . . . . 15–5
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 setup for MicroStation . . . . . . . . . . . . . . 12–6
design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 SQL Report*Writer . . . . . . . . . . . . . . . . . 11–7
directory structure . . . . . . . . . . . . . . . . . . 6–2 SQL*Forms . . . . . . . . . . . . . . . . . . . . . . . 11–7
file duplication . . . . . . . . . . . . . . . . . . . . . 6–4 SQL*ReportWriter . . . . . . . . . . . . . . . . . 15–5
maintain . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 OrderBy Clause . . . . . . . . . . . . . . . . . . . . . 13–7
remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 Orphan Linkage . . . . . . . . . . . . . . . . . . . . . 14–4
sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–7
sample workspace . . . . . . . . . . . . . . . . . . . 3–6 manipulate elements with . . . . . . . . . . . 14–8
Move remove . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–9
fixed point . . . . . . . . . . . . . . . . . . . . . . . . 6–17 OX= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
MSCATALOG
add row to . . . . . . . . . . . . . . . . . . . . . . . 13–37
P
dastable column . . . . . . . . . . . . . . . . . . 13–34
entitynum column . . . . . . . . . . . . . . . . 13–32 palettes, converting to tool boxes . . . . . . . . 4–1
fencefilter column . . . . . . . . . . . . . . . . . 13–33 Paper Menu . . . . . . . . . . . . . . . . . . . . . . . . 4–30
formtable column . . . . . . . . . . . . . . . . . 13–34 Parameter Constraints Tool Box . . . . . . . . 6–23
maintain . . . . . . . . . . . . . . . . . . . . . . . . 13–35 Assign Equation . . . . . . . . . . . . . . . . . . . 6–25
nextocc column . . . . . . . . . . . . . . . . . . . 13–44 Assign Variable to Dimensional
reporttable column . . . . . . . . . . . . . . . . 13–33 Constraint . . . . . . . . . . . . . . . . . . . . . . 6–26
screenform column . . . . . . . . . . . . . . . . 13–33 Convert Dimension to Constraint . . . . . 6–24
sqlreview column . . . . . . . . . . . . . . . . . 13–33 Paste
structure . . . . . . . . . . . . . . . . . . . . . . . . 13–31 bit-mapped graphic . . . . . . . . . . . . . . . . 5–65
tablename column . . . . . . . . . . . . . . . . 13–32 from clipboard . . . . . . . . . . . . . . . . . . . . . 5–63
msconfig.cfg . . . . . . . . . . . . . . . . . . . . . . . . 3–39 Paste Special dialog box . . . . . .5–73 thru 5–74
mslink . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30 Pattern
key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30 stroke . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–79
key value . . . . . . . . . . . . . . . . . . . . . . . . . 14–9 Place
next available number . . . . . . . . . . . . . 13–44 image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–65

Index
PLACE SMARTLINE . . . . . . . . . . . . . . . . 4–48 Re-solve Constraints . . . . . . . . . . . . . . . . . 6–43
Point REDFILE OFF . . . . . . . . . . . . . . . . . . . . . . 5–84
constrain . . . . . . . . . . . . . . . . . . . . . . . . . 6–38 REDFILE ON . . . . . . . . . . . . . . . . . . . . . . . 5–84
constrain to lie at center of circle . . . . . 6–40 Reference File Agent
constrain two to same location . . . . . . . 6–40 load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–6
fix at location . . . . . . . . . . . . . . . . . . . . . 6–41 Reference Files
symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–76 embedded . . . . . . . . . . . . . . . . . . . . . . . . 5–71
Point Symbol . . . . . . . . . . . . . . . . . . . . . . . 6–68 Relational Database . . . . . . . . . . . . . . . . . . 11–4
associate with stroke . . . . . . . . . . . . . . . 6–78 strengths . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
base stroke pattern . . . . . . . . . . . . . . . . . 6–77 table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–79 Rendering Settings
horizontal offset . . . . . . . . . . . . . . . . . . . 6–78 pattern/bump maps . . . . . . . . . . . . . . . . 6–96
justification . . . . . . . . . . . . . . . . . . . . . . . 6–78 Report
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–79 formatting and output with database
offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78 products . . . . . . . . . . . . . . . . . . . . . . . . 15–4
origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–78 generate . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
rotation angle . . . . . . . . . . . . . . . . . . . . . 6–78 Report Table . . . . . . . . . . . . . . . . . . . . . . . . 15–1
vertical offset . . . . . . . . . . . . . . . . . . . . . 6–78 generate . . . . . . . . . . . . . . . . . . . . . . . . . 15–2
private key, for digital signatures . . . . . . 6–107 name . . . . . . . . . . . . . . . . . . . . . . 15–2, 13–33
Profile RESET DIMENSION . . . . . . . . . . . . . . . . 6–54
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–45 Resources
sketch . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17 archiving classes . . . . . . . . . . . . . . . . . . 6–113
Profile Tool Box . . . . . . . . . . . . . . . . . . . . . 6–16 Review Attributes . . . . . . . . . . . . . . . . . . 13–14
Convert Element to Profile . . . . . . . . . . 6–22 Review Database Attributes of Element . 14–1
Sketch Profile . . . . . . . . . . . . . . . . . . . . . 6–17 RIS . . . . . . . . . . . . . . . . . . . . . . . . . 11–5, 11–11
Project application . . . . . . . . . . . . . . . . . . . . . . 11–11
configuration file . . . . . . . . . . 1–1, 3–5, 6–96 client . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11
custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 client and runtime package . . . . . . . . . 11–12
file sharing among . . . . . . . . . . . . . . . . . . 6–4 common interface . . . . . . . . . . . . . . . . . 11–11
in workspace . . . . . . . . . . . . . . . . . . . . . . . 1–4 data server . . . . . . . . . . . . . . . . . . . . . . 11–11
module data . . . . . . . . . . . . . . . . . . . . . . . 3–6 Development Platform . . . . . . . . . . . . . 11–12
sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–11 INFORMIX and . . . . . . . . . . . . . . . . . . 11–11
public key, for digital signatures . . . . . . . 6–107 Oracle and . . . . . . . . . . . . . . . . . . . . . . . 11–11
parts of interface . . . . . . . . . . . . . . . . . 11–11
Q Report Writer . . . . . . . . . . . . . . . . . . . . 11–12
Query Statements schema . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
opening . . . . . . . . . . . . . . . . . . . . . . . . . 13–21 setup for MicroStation . . . . . . . . . . . . . 12–10
saving . . . . . . . . . . . . . . . . . . . . . . . . . . 13–21 tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–12
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . 11–12
R Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
attach to element . . . . . . . . . . . . . . . . . 13–39
RA= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1
detach from element . . . . . . . . . . . . . . . . 14–4
Raster File
seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–40
formats supported . . . . . . . . . . . . . . . . . 5–59
selection criteria . . . . . . . . . . . . . . . . . . . 14–1
Rdb
Row Navigation . . . . . . . . . . . . . . . . . . . . 13–14
interface through RIS . . . . . . . . . . . . . . 11–11

Index
S Sketch Profile . . . . . . . . . . . . . . . . . . . . . . . 6–17
Save SQL
image file . . . . . . . . . . . . . . . . . . . . . . . . . 5–59 command file . . . . . . . . . . . . . . . . . . . . . 13–27
Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5 SQL Statement . . . . . . . . . . . . . . . . . . . . . 13–22
Save Settings . . . . . . . . . . . . . . . . . . . . . . . . 6–6 commit . . . . . . . . . . . . . . . . . . . . . . . . . . 13–28
Scale COMMIT . . . . . . . . . . . . . . . . . . . . . . . . 13–24
modify settings group . . . . . . .6–87 thru 6–88 CONNECT . . . . . . . . . . . . . . . . . . . . . . 13–25
settings group . . . . . . . . . . . . .6–87 thru 6–88 CREATE TABLE . . . . . . . . . . . 13–24, 13–29
Screen Capture . . . . . . . . . . . . . . . . . 5–55, 5–58 DELETE . . . . . . . . . . . . . . . . . . . . . . . . 13–23
image file format . . . . . . . . . . . . . . . . . . 5–59 DISCONNECT . . . . . . . . . . . . . . . . . . . 13–25
menu (pull-down) . . . . . . . . . . . . . . . . . . 5–58 DROP . . . . . . . . . . . . . . . . . . . . . . . . . . 13–24
rectangular area in view . . . . . . . . . . . . 5–58 INSERT . . . . . . . . . . . . . . . . . . . . 14–3, 13–23
view window . . . . . . . . . . . . . . . . . . . . . . 5–58 manually commit . . . . . . . . . . . . . . . . . 13–28
Screen Form MicroStation-specific . . . . . . . . . . . . . . 13–25
locate . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–34 RELOAD . . . . . . . . . . . . . . . . . . . . . . . . 13–25
table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–34 ROLLBACK . . . . . . . . . . . . . . . . . . . . . 13–25
Seed File SELECT . . . . . . . . . . . . . . . . . . 13–23, 13–33
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 submit . . . . . . . . . . . . . . . . . . . . . . . . . . 13–26
default . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–96 UPDATE . . . . . . . . . . . . . . . . . . 13–23, 13–41
default directory . . . . . . . . . . . . . . . . . . . 6–96 SQL Window . . . . . . . . . . . . . . . . . . . . . . . 13–25
design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 SQL*Forms . . . . . . . . . . . . . . . . . . . . . . . . . 11–7
sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 STEP AP203/214 . . . . . . . . . . . . . . . . . . . . 5–47
Select Stroke Pattern . . . . . . . . . . . . . . . . . . . . . . 6–67
table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3 base for point symbol component . . . . . 6–77
Sending Application . . . . . . . . . . . . . . . . . . . 5–4 bypass corner . . . . . . . . . . . . . . . . . . . . . 6–72
Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–5 delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–75
Settings File . . . . . . . . . . . . . . . . . . . . . . . . . 5–7 modify . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–75
export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7 stroke end cap . . . . . . . . . . . . . . . . . . . . . 6–72
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7 stroke length . . . . . . . . . . . . . . . . . . . . . . 6–72
Settings Group stroke width . . . . . . . . . . . . . . . . . . . . . . 6–72
categories . . . . . . . . . . . . . . . . . . . . . . . . 6–86 Style
create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–86 menu in Workspace . . . . . . . . . . . . . 1–1, 1–6
define/modify scale . . . . . . . . .6–87 thru 6–88 Sybase
scale . . . . . . . . . . . . . . . . . . . . .6–87 thru 6–88 interface through RIS . . . . . . . . . . . . . . 11–11
Settings Menu
Color Table . . . . . . . . . . . . . . . . . . . . . . . 6–62 T
Level > Names . . . . . . . . . . . . . . . . . . . . 6–56 Tab Page
Manage . . . . . . . . . . . . . . . . . . . . . . . . . . 6–84 where . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
Shadow Map . . . . . . . . . . . . . . . . . . . . . . . . 6–96 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
Shape column . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4
construct attached . . . . . . . . . . . . . . . . . 6–28 create . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–29
Sheet File displayable attribute . . . . . . . . . . . . . . . 14–2
seed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5 index . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–30
SHOW WEBTAGS . . . . . . . . . . . . . . . . . . . . 7–3 join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
SKETCH . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22 name . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–32

Index
primary key . . . . . . . . . . . . . . . . . . . . . . 13–30 create . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44
row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–4 display information . . . . . . . . . . . . . . . . 4–43
select . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3 execution . . . . . . . . . . . . . . . . . . . . . . . . . 4–41
Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1 graphic selection field . . . . . . . . . . . . . . . 4–41
report template . . . . . . . . . . . . . . . . . . . . 6–96 key entry field . . . . . . . . . . . . . . . . . . . . . 4–41
TB= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–81 output field . . . . . . . . . . . . . . . . . . . . . . . 4–41
Text servicing application . . . . . . . . . . . . . . . 4–41
import . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–81 text node . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
include from file . . . . . . . . . . . . . . . . . . . 5–81
Text Node U
displayable attribute . . . . . . . . . . . . . . . 14–2 UC= . . . . . . . . . . . . . . . . . . . . . . . .9–4 thru 14–5
tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42 UCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
Tool User Command . . . . . . . . . . . . . . . . . . . . . . 9–3
associated key-in . . . . . . . . . . . . . 4–11, 4–14 activate . . . . . . . . . . . . . . . . . . . .9–4 thru 9–5
changing its description . . . . . . . . . . . . . 4–13 compile . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
deleting from list box . . . . . . . . . . . . . . . . 4–9 edit index file . . . . . . . . . . . . . . . . . . . . . . 9–5
frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 hilite . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5
icon . . . . . . . . . . . . . . . . . . . . . . . . 4–11, 4–13 index file . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
inserting . . . . . . . . . . . . . . . . . . . . . . . . . 4–10 run . . . . . . . . . . . . . . . . . . . . . . . .9–4 thru 9–5
modify icon . . . . . . . . . . . . . . . . . . . . . . . 4–13 User Configuration File . . . . . . . . . . . . . . . . 3–5
size . . . . . . . . . . . . . . . . . . . . . . . . . 4–11, 4–14 User Interface
Tool Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 customize . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Attach Element . . . . . . . . . . . . . . . . . . . . 6–27 modifications file . . . . . . . . . . . . . . . . . . 3–36
child . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5, 4–8 select in workspace . . . . . . . . . . . . . . . . . . 1–1
converting custom palettes to . . . . . . . . . 4–1 User Menu
customize . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 Utilities Edit UCM Index File . . . . . . . . . 9–5
Evaluate Constraints . . . . . . . . . . . . . . . 6–42 User Preferences . . . . . . . . . . . . . . . . . . . . . 1–1
frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 file . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1, 3–38
Geometric Constraints . . . . . . . . . . . . . . 6–32 USERCOMMAND . . . . . . . . . . . . . . . . . . . . 9–4
insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8 Utilities
Modify Constraint . . . . . . . . . . . . . . . . . 6–47 screen capture . . . . . . . . . . . . . . . . . . . . . 5–55
Parameter Constraints . . . . . . . . . . . . . 6–23 Utilities Edit UCM Index File . . . . . . . . . . . 9–5
Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16 Utilities Menu
rearrange . . . . . . . . . . . . . . . . . . . . . . . . . 4–8 MDL Applications . . . . . . . . . . . . . . . . . . 10–2
Redline . . . . . . . . . . . . . . . . . . . . . . . . . . 5–83 Utility
restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5 Database Verification ("dbcheck.ma") . . 14–6
Tools Menu
Engineering Links . . . . . . . . . . . . . . . . . . 7–1 V
Trim
V5 menus
Constrained Geometry . . . . . . . . . . . . . . 6–49
importing . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
TrueType fonts, MicroStation support of . 5–72
V5 palettes
Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41
converting to a tool box . . . . . . . . . . . . . . 4–7
action types . . . . . . . . . . . . . . . . . . . . . . . 4–48
importing . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
build . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44
Variable, assign to dimensional constraint 6–26
cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
View
control information . . . . . . . . . . . . . . . . . 4–42

Index
capture contents of . . . . . . . . . . . . . . . . . 5–58 Architecture . . . . . . . . . . . . . . . . . . . . . . . 2–2
capture with border . . . . . . . . . . . . . . . . 5–58 AutoCAD Transition . . . . . . . . . . . . . . . . . 2–9
send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–67 Civil Engineering . . . . . . . . . . . . . . . . . . 2–10
view objects . . . . . . . . . . . . . . . . . . . . . . . . . 5–67 components . . . . . . . . . . . . . . . . . . . . . . . . 1–1
View Objects configuration . . . . . . . . . . . . . . . . . . . . . . . 3–1
edit embedded . . . . . . . . . . . . . . . . . . . . . 5–69 configuration file . . . . . . . . . . . . . . . . . . . 1–1
edit linked . . . . . . . . . . . . . . . . . . . . . . . . 5–70 create . . . . . . . . . . . . . . . .1–8, 1–10 thru 1–11
editing in other applications . . . . . . . . . 5–69 Learning . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
embed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–69 Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–69 Mechanical Drafting . . . . . . . . . . . . . . . . 2–23
updating . . . . . . . . . . . . . . . . . . . . . . . . . 5–70 menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
views module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
sending to other applications . . . . . . . . . 5–67 project component . . . . . . . . . . . . . . . . . . . 1–1
Visual SQL Query Builder . . . . .13–1 thru 13–2 sample components . . . . . . . . . . . . 2–1, 1–11
SELECT statements . . . . . . . . . . . . . . . . 13–3 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
VSQL OPEN . . . . . . . . . . . . . . . . . . . . . . . . 13–1 style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
user interface component . . . . . . . . . . . . . 1–1
W user preferences component . . . . . . . . . . 1–1
WHERE Clause . . . . . . . . . . . . . . . . . . . . . 13–7 Workspace Menu
Window Configuration . . . . . . . . . . . . . . . . . 10–4, 3–7
capture . . . . . . . . . . . . . . . . . . . . . . . . . . 5–59 Customize . . . . . . . . . . . . . . . . . . . . 4–2, 4–23
Windows Explorer . . . . . . . . . . . . . . . . . . 6–112 Function Keys . . . . . . . . . . . . . . . . . . . . . 4–27
Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

MSJ Adminguide PDF

Uploaded by

Copyright:

Available Formats

MSJ Adminguide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSJ Adminguide PDF

Uploaded by

Copyright:

Available Formats

MicroStation/J®

Java™ and all Java-based trademarks and logos are trademarks

Windows is a registered trademark of Microsoft® Corporation.

Other brands and product names are the trademarks of

United States Patent Nos. 5,815,415 and 5,784,068.

MicroStation/J Administrator’s Guide

2. Sample Workspace Components

MicroStation/J Administrator’s Guide i

Introductory Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15

ii MicroStation/J Administrator’s Guide

4. Customizing the User Interface

MicroStation/J Administrator’s Guide iii

Part II: Exchanging and Sharing Data

5. Exchanging Data with Other Applications

iv MicroStation/J Administrator’s Guide

Settings files for CALS export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–30

MicroStation/J Administrator’s Guide v

Using Redline Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–82

6. Building Custom Projects

vi MicroStation/J Administrator’s Guide

Make Construction or Parameter Invariant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38

MicroStation/J Administrator’s Guide vii

The archive process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–99

Part III: Internet Technologies

8. Publishing Data to the Internet

viii MicroStation/J Administrator’s Guide

Part IV: Using Software Extensions

9. Scripts, Macros, and User Commands

10. MDL Applications

Part V: External Database Interface

11. MicroStation and Non-graphical Data

MicroStation/J Administrator’s Guide ix

12. Connecting to Databases

13. Linking Database Rows to Elements

x MicroStation/J Administrator’s Guide

Command files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–27

14. Querying and Maintaining the Database

MicroStation/J Administrator’s Guide xi

15. Generating Reports

16. Database Application Software

xii MicroStation/J Administrator’s Guide

• The sample workspaces are covered in Sample Workspace

• The parts of a workspace and basic procedures for selecting them

• The nature of the sample workspaces delivered

A workspace is a custom MicroStation “environment” or configuration.

For example, MicroStation is delivered with a sample “architecture”

You can also create your own MicroStation environments

MicroStation/J Administrator’s Guide 1–1

2 . Project — A project consists of customized data files, such as

3 . Interface — A customized user interface (defined in

4 . Style — MicroStation either opens a Status Bar or a Command

5 . (User) Preferences — Customized user preferences defined

The name of the user configuration file is used as the name of

Setting up the workspace

1–2 MicroStation/J Administrator’s Guide

The following chart cross references the 5.0 functions

Combo box Equivalent to Version 5.0 action

Locating the components of the workspace combo boxes

MicroStation/J Administrator’s Guide 1–3