Follow these steps when checking your MicroStation GeoGraphics project after you have completed the instructions from Appendix B: Using MGE Projects in MicroStation GeoGraphics from the MicroStation GeoGraphics User's Guide.
The Verify Tables settings box can be found under the Tables menu in the Project Setup dialog. This tool will verify that you have a one-to-one relationship between the CATEGORY and UG_CATEGORY tables, the FEATURE and UG_FEATURE tables, and the MAPS and UG_MAPS tables.
These tables contain the MicroStation GeoGraphics data model extensions that enable them to work with MGE. Verify Tables will find any incompatibility between these and will give you the option to either delete or insert the accompanying row to fix the table relationship.
Any table names in the MSCATALOG that call bogus table names will produce errors. Also, the only MicroStation GeoGraphics system tables that should be referenced in MSCATALOG are CATEGORY, FEATURE, and MAPS. No other system tables should be listed! MSCATALOG should only list tables that are linked to graphics (not joined tables, UG_ tables, etc.)
This table is needed so the SQL Manager and Query Builder can be used with your user attribute tables. You may also specify an alias and your primary key column here.
If you populate this table in your database software, you will notice a USTN column. This column is used to flag tables that are linked to MicroStation graphics. If "1" is entered in this column, the Query Builder--when opened--will show the word "USTN" to the right of the table name, which means the table is linked to graphics.
It is also a good rule of thumb to capitalize everything in this table. Make sure the column words MSLINK and MAPID are also capitalized in the user attribute tables. Always make sure that your user attribute tables have MSLINK and MAPID columns when linked to graphics. It is important that the MAPID column value is the value from the MSLINK column in the MAPS table for the corresponding map you are using.
When tables are imported through ODBC from databases like Oracle into Microsoft Access 7.0, Access 7.0 will sometimes pad columns with spaces. For example if you had a column length set to 50 characters and had the word ROAD1 in the column, Access 7.0 would fill the remaining 45 empty characters with spaces. MicroStation will try to read these spaces upon startup and generate errors. These spaces must be trimmed in Access for the tables to work properly with MicroStation. The tables to concentrate on when looking for spaces would be the system tables (such as MSCATALOG, MAPS, etc.). These are obviously the most important for a successful project load. Access 2.0 does not have this problem of padding columns with spaces.
MGE join catalog tables like JOIN_CAT are not used in MicroStation GeoGraphics. You must enter your join relationships in the GeoGraphics UGJOIN_CAT table for them to be recognized.
Maps that have been registered and since removed from the project will still have a row that they were linked to in the MAPS and UGMAP tables. When the MAP MANAGER is invoked and the ALL option is chosen, these old map names will show. It is good practice to delete these rows from the MAPS table and their corresponding rows in the UGMAP table after the unwanted DGN file has been removed; otherwise MicroStation GeoGraphics thinks the map is still there.
Also, make sure the LSNAME (for custom line style name) column in UGFEATURE is set to a character type, not a numeric type. If you are having problems inserting new features and suspect invalid column types, examine the delivered MYTOWN dataset column types as a guide to modify your feature tables.
These steps can be used as set-up guidelines after running the MGE extension script as outlined in Appendix B: Using MGE Projects in MicroStation GeoGraphics from the MicroStation GeoGraphics User's Guide.
Product TechNotes and FAQs
Geospatial Product TechNotes And FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!