How does the intermediate geodatabase (.mdb) file function in WaterGEMS for ArcMap?

  Applies To 
  Product(s): WaterGEMS, SewerGEMS, HAMMER
  Version(s): 08.11.XX.XX
  Original Author: Mark Pachlhofer, Bentley Technical Support Group


How does the geodatabase (.mdb) file function in the ArcMap Platform of WaterGEMS, SewerGEMS and HAMMER? Why do I need to select a .MDB file when setting up a model in WaterGEMS, SewerGEMS or HAMMER for ArcMap?


The geodatabase MDB file that you create when creating or opening a hydraulic model acts as an intermediate file that allows ArcMap to communicate data from and to the WaterGEMS, SewerGEMS or HAMMER database file. In the latest versions of WaterGEMS, SewerGEMS and HAMMER, ( + for WaterGEMS and HAMMER) the model database is the file with extension .SQLITE and for previous versions the model file extension was .MDB.

The attributes that get included in this geodatabase (which can then be color coded and annotated on) are controlled by the GeoTables.


  1. The model database and the ArcMap Geodatabases are separate files.
  2. The intermediate Geodatabase should be kept separate from any other geodatabase you may have. Meaning, you should choose to create a new geodatabase (preferably in the same folder as the hydraulic model, with an obvious name like "<modelname>GDB.MDB") rather than utilize an existing geodatabase.
  3. If a problem occurs with your hydraulic model when integrated with ArcMap (for example the table of contents appears to have duplicate entries for the hydraulic element types, or generally things are not working correctly) you can close the program, delete the geodatabase, then re-add the project in the "For ArcMap" interface and create a new geodatabase.

The file is first created at the initial attach geodatabase dialog shown below:

The graphic below shows how this relationship works:

See Also

WaterGEMS for ArcMap FAQ

SewerGEMS For ArcGIS [FAQ]

What is a GeoTable?

Not all model properties are available when color coding or annotating in ArcMap