Page History
...
| Topic | Description |
|---|---|
| Add Base Attributes to Person Entity | Adds base attributes to selected entities, which represent people. It will also introduce a primary key based upon the entity's name. |
| Add Definition to Type Entities | Add a definition to selected entities. The definition applied to the selected entity will also include the object's name automatically, as in "My definition text + entity name +(s)" |
| Add Parent Name Prefix to Propagating Key | Add the entity name as a prefix to all attribute role names. It demonstrates how to use the FKColumnPair object |
| Add Table Name Prefix Globally | Add a prefix string to the names of all entities in the model. The macro opens a dialog box prompting the user for the prefix. If the current active model is logical, it will assign the prefix to all entity names. If the current model is physical, it will assign the prefix to all table names. |
| Add Table Name Prefix Selectively | Add a prefix string to the names of selected entities in the model. The macro opens a dialog to prompting the user for the prefix. If the current model is logical, it assigns the prefix to selected entity names. If the current model is physical, it will assign the prefix to selected table names. |
| Add Table Owner Globally | For physical models, this will update the owner field in the table editor for all tables in the active model. The active model must be a physical model. |
| Add View Owner Selectively | For physical models, this will update the owner field in the view editor for all selected entities. The active model must be a physical model. |
| Attachment Example | Exports attachment data for each bound attachment for every selected table in the active model. The file name and path is "C:\Attachment Data.txt. |
| Attribute Binding Macro | Lists all the unbound attributes/columns of all the models (logical and all physicals) and domains. The attributes can then be bounded to any of listed domains by pressing the "Bind" button. |
| Auto-Align Selected Entities Left | Performs the align left' operation (similar to the align buttons on the Alignment Toolbar) for all selected entities. This macro demonstrates more on how to use entity display objects. |
| Auto-Color All Entities with FKs | Make all entities with foreign keys purple. It will first select (highlight) all entities in the current, submodel. Then it will make all selected entities with foreign keys (which, in this case, are all the entities in the submodel) purple. Finally, it will deselect (unhighlight) all entities in the current, active submodel. This macro illustrates how to use entity objects, entity display objects, and selected objects - and how to distinguish among 'them. |
| Auto-Combine Selected Entities | Takes all the attributes from all the selected entities and add them into one newly created entity. Includes a separate function GetAveragePoint(), this function will get the average x or y coordinate point among all selected entities. The second parameter determines whether to calculate the average x coordinate or the average y coordinate. |
| Auto-Convert Datatype | Iterate through all the selected entities and change the datatypes for all attributes which use VARCHAR to TEXT. |
| Auto-Create Data Dictionary and Bound Domain | Creates a new diagram, then create a rule, default and domain in the data dictionary. Then it will bind the rule and default to the domain. Next, it will then create an entity and an attribute. Finally, it will bind the domain to the attribute. |
| Auto-Create Data Dictionary | Creates a user-defined data dictionary quickly. The macro can be used as a template to create user-defined or business-specific data dictionaries. This macro can be inserted into ER/Studio's ERSBasicHandlers system (specifically in the '"CreateDiagramHandler(CurDiagram As Object)" section of ERSBasicHandlers) and if the Create Handlers option is checked on in ER/Studio's Automation Interface Options, this Data Dictionary will be created and populated any time a user creates a new diagram. |
| Auto-Create New Diagram | Creates a new diagram. The new diagram will contain an IBM DB/2 physical model and six entities in the physical model. |
| Constraint Generator | Generates constraints from the defined reference values. The reference values must be defined in the data dictionary of ER/Studio. The macro can select from bound attributes, all attributes, bound domains or all domains. This is chosen with the radio buttons at the bottom of the dialog. the constraint will be inserted in the check constraint/rule tab of the domain or attribute. |
| Convert Name Case | Converts the case of Attributes, Columns and Entity/Table names for the highlighted tables/Entities in the active SubModel to all upper or lower case. Works in Logical or Physical models |
| Definition Editor | Lists all the tables and allows the user to update the definition field for the table, by pressing the "update" button. There will also be a list of columns for the respective table, that the user can use to update the definitions for each column. This macro will run on a logical or a physical model and populate the lists accordingly. |
| Domain Bindings Export to Excel | Lists all the tables and allow the user to update the definition field for the table, by pressing the "update" button. There will also be a list of columns for the respective table, that the user can use to update the definitions for each column. This macro will run on a logical or a physical model and populate the lists accordingly. |
| Domain Bindings Import from Excel | Exports domain bindings for all the attributes in the current model. The existing columns in the spread sheet must be left in the same format if the bindings are going to be used to import back into a model. Note that the attribute data type is only in the spread sheet for informational purposes when refactoring attributes and columns and assigning them to domains. |
| Domain Bindings | Imports domain bindings from Excel. I will map domains to attributes or columns depending on the data in the spread sheet. The macro provides an interface to select the dictionary where the domains are located and the model to search for the attributes or columns. When importing into a physical model the spread sheet must have the physical table and column names that match the selected physical model. When importing into the logical model, the names in the spread sheet must match the entity and attribute names. |
| Example Macro: Loop through Objects of Active Submodel | Brings up a dialog box that shows all attributes bounded to a selected domain. It also allows the user to unbind specific attributes from the selected domain. The dialog box contains two list boxes and two buttons. The first list box, "Domains", shows all the domains in the diagram. The second list box, "Bounded Attributes", shows all the attributes bounded to the selected domain in the "Domains" list box. There is also an "OK" button and an "UnBind" button. The user can press the "UnBind" button to unbind selected attributes in the "Bounded Attributes" list box from the selected domain in the "Domains" list box. |
| Export Domain Info to Excel | Exports the domains and their properties to excel. Each record in the Excel spread sheet represents on domains from the data dictionary. The spread sheet can be used to store domains outside of ER/Studio. The domain properties can be updated in the spread sheet and imported back into an existing model or a new model using the "Import Domains From Excel" macro. The columns in the spread sheet must remain in the same order to import them properly. REQUIREMENT: You must have MS Excel 97 or later installed. |
| Export Index Column Info to Excel | Generates an index column report for the active model in ER/Studio. Each record in the Excel spread sheet represents an indexed column. The spread sheet can be used to apply naming conventions to indexes. The new index name can be read in with the "Import Index Names from Excel" macro from the "New Index Name" column in the spread sheet. REQUIREMENT: You must have MS Excel 97 or later installed |
...
The following examples demonstrate various methods of importing and exporting model meta data with MSOffice applications such as Excel and Word. Importing has such uses as transferring spreadsheets or lists of names and attributes into your model. Exporting might be used for a presentation or report.
...
...
- Export Metadata to Excel Version 3.1
- Export Model Metadata to Excel
- Export Model Metadata to Word
- Export Object Definitions and Notes to Excel
- Export Reference Value Info to Excel
- Export Relationship Info to Excel
- Import Domains from Excel
- Import Index Names from Excel
- Import Object Definitions and Notes from Excel
- Import Reference Values from Excel
- Import Relationship Names from Excel
- Submodel Report
Pre/PostSQL Demonstrations for Selected Target Databases
...