Historically Microsoft Access Database files (MDB) have been used to store symbol text attributes, drawing mode definitions, and catalog item descriptions. Refer to chart below for more details.
In large muti-user environments these Microsoft Access Database files can become cumbersome causing system administrators to perform periodic file maintenance, such as, compacting and repairing MDB files.
Data (Contents stored in MDB)
Multi_Language_UI.mdb
Catalog.mdb
Symbol Text Attributes
X
Symbol Mode Definitions
Language Phrase Translations
Dialog Box Text and Captions
Device Family Descriptions
Macro Descriptions
Symbol Descriptions
Symbol Categories
Title Block Configuration Information
Note: Your environment may have multiple Catalog.mdb files. A single Catalog.mdb file will reside in each Catalog folder.
Two new configuration variables are now available to control the file type used for Multi_Language_UI.mdb and Catalog.mdb’s.
Set variable value = 1 to use txt files instead of MDB files. When variable does not exist in your configuration or value = 0, the application will use MDB format.
These variables can be added to the following configuration files:
Configuration File
Default File Location
WorkSpaceSetup.cfg
$\ProgramData\Bentley\Promise CONNECT Edition\Configuration
$$WorkSpaceName$$.cfg
$\ProgramData\Bentley\Promise CONNECT Edition\Configuration\Workspaces
Promise.cfg
$\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\$$WorkSpaceName$$\Standards\Promise
$ - Drive where application is installed
$$WorkSpaceName$$ - Name of Workspace. Example: Promise ANSI-IEEE Example.cfg
1. Determine if your environment uses a ProjectWise Managed workspace to store Multi_Language_UI.mdb or Catalog.mdb’s.
MDB File
$\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\$$WorkSpaceName$$\Standards\Promise\Databases
$\ProgramData\Bentley\Promise CONNECT Edition\Configuration\WorkSpaces\$$WorkSpaceName$$\Standards\Promise\Catalogs\$$CatalogName$$
2. If using ProjectWise Managed Workspace, you must export a copy of your Catalog.mdb’s and Multi_Language_UI.mdb files to a drive. (can be network or local)
3. Open MDB to TXT conversion tool. Locate Mdb2Txt.exe in folder "C:\Program Files\Bentley\Promise CONNECT Edition\Promise\Assemblies"
4. Select desired Catalog.mdb file using browse button..
5. Click Convert. Then Click OK.
6. Verify conversion. Open Catalog folder using Windows explorer. Verify that the following txt files exist.
7. Repeat Steps 4 through 6 for each Catalog within your configuration.
8. Select desired Multi_Language_UI.mdb file using browse button.
9. Click Convert. Then Click OK.10. Verify conversion. Open Databases folder using Windows explorer. Verify creation of new folder and txt files. New Folder
New Folder Contents11. Add configuration variables to one of the three *.cfg files mentioned in beginning of this document.
Use below Text to Copy into *.CFG file txtMultiLanguage = 1
txtCatalog = 1
Example edit made to Promise.cfg file.
12. Change ELEC_LANGUAGE_DB_PATH variable value. This variable resides in Promise.cfg.
Set this variable’s value equal to the folder path of your Mutli_Language folder. Copy below text to Promise.cfg file to replace with existing cfg as highlighted in the below reference images.
ELEC_LANGUAGE_DB_PATH = $(AppWorkspaceStandards)Databases/Multi_Language_UI/
Before Edit
After Edit
Note: If there is a need to modify the “Multi_Language_UI” folder, then update the configuration variable with correct details. Example if the folder is renamed to “Custom_ Multi_Language_UI” then the configuration variable should be set to “ELEC_LANGUAGE_DB_PATH = $(AppWorkspaceStandards)Databases/Custom_Multi_Language_UI/”13. If using ProjectWise Managed workspace, import the Mutli_Language folder , all Catalog txt files, and Promise.cfg into your Managed configuration. Users should receive the updated configuration the next time they open Promis.e CONNECT.