Appendix > Parameter Files

The DBWAppUser.par file

This file makes possible overriding some user-interface parameters, that could have a different value from the defaults values written in the global DBWAPP.PAR parameters file.

MechworksPDM looks for a file named DBWAPPUSER.PAR in the USERS\<user name>\... directory, and, if existing, it overrides the actual global values with the ones defines in this new file.

The overrideable options allowed in this file are:

ALWAYS_OPEN_BROWSER_IN_TREE_PAGE

ALWAYS_OPEN_BROWSER_ONLY_WITH_ONE_PROJECT
AVOID_AUTOMATIC_COLUMN_RESIZING
AVOID_AUTOMATIC_REFRESHING_OF_COMPOSED_OF_USED_BY_LISTS
AVOID_AUTOMATIC_REFRESHING_OF_COMPOSED_OF_USED_BY_LISTS_FOR_PROJECTS
DATABASE_USER_INTERFACE_LOCALIZATION
DISABLE_ASSEMBLY_GRID
DISABLE_DRAWING_GRID
DISABLE_GENERIC_GRID
DISABLE_PART_GRID
ENABLE_AUTOMATIC_ROW_RESIZING
ENABLE_DRAG_AND_DROP_IN_GRIDS
ENABLE_DRAG_AND_DROP_IN_TREE
ENABLE_DRAG_AND_DROP_ON_ASSEMBLIES_IN_TREE
EXPAND_CURRENT_PROJECT_IN_TREE
EXTRA_FIELDS_TO_SHOW_IN_TREE
EXTRA_FIELDS_TO_SHOW_IN_TREE_COLUMNS
HIDE_QUERY_PAGE_SQL_WINDOW
HIDE_USED_BY_LIST_IN_DATA_INPUT_FORM
MAX_SUBPROJECTS_LEVELS_IN_TREE
MINIMIZE_BROWSER_ON_OPEN
OK_DATABASE_USER_INTERFACE_LOCALIZATION
OK_UNICODE_USER_INTERFACE_LOCALIZATION
OK_UNICODE_USER_INTERFACE_LOCALIZATION_DISPLAY_BOTH
OK_UNICODE_USER_INTERFACE_LOCALIZATION_ONLY_BOMTITLE
SHOW_BOM_COUNT_IN_TREE
SHOW_BROWSER_AS_MDI_CHILD_WINDOW
SHOW_COMPANY_ID_IN_TREE
SHOW_DBWERP_STATE_IN_TREES_AND_GRIDS
SHOW_DESCRIPTION_IN_PROJECT_TREE
SHOW_DESCRIPTION_IN_TREE
SHOW_DIRTY_REVISION_FLAG_IN_TREE
SHOW_DRAWINGS_IN_PROJECT_TREE
SHOW_EXISTING_DRAWINGS_IN_TREE
SHOW_FAKE_COMPONENTS_IN_TREE
SHOW_FIND_DIALOG_ON_EXPLORE
SHOW_FIND_DIALOG_ON_EXPLORE
SHOW_MAKE_BUY_IN_TREE
SHOW_ONLY_DESCRIPTION_IN_PROJECT_TREE
SHOW_ONLY_TOP_LEVEL_OBJECTS_IN_PROJECT_TREE
SHOW_PHYSICAL_QUANTITY_IN_TREE
SHOW_REVISION_IN_TREE
UNICODE_USER_INTERFACE_LOCALIZATION
USE_INTELLIGENT_MENUS
WRAP_BROWSER_GRID_TEXT

This mechanism MUST be used with the master global parameter file DBWAPP.PAR kept in READ-ONLY state, otherwise any DBWAPPUSER.PAR defined parameter will be saved in the DBWAPP.PAR as well.

Example

Suppose a particular user ( named Joe ) has a two-monitors computer, so he wants to work with the option

SHOW_BROWSER_AS_MDI_CHILD_WINDOW

set to 0, even if the default value, stored in the DBWAPP.PAR, is 1 for all the remaining users. More, he likes the Document Page as default page, so he wants to have the

ALWAYS_OPEN_BROWSER_IN_TREE_PAGE

always set to 0. The DBWorks Administrator will create the following DBWAPPUSER.PAR file:

;

;
; DBWAPPUSER.PAR - DBWORKS (C)MechWorks user overrideable parameters file
;
;
SHOW_BROWSER_AS_MDI_CHILD_WINDOW 0
ALWAYS_OPEN_BROWSER_IN_TREE_PAGE 0
<empty line>

and he will place it in the <GlobalParametersPath>\USERS\Joe\ folder.

Overriding Options→User settings

The DBWAPPUSER.PAR can contain also any Options→User Options parameters that must be set on each user workstation.
For example, setting a line like:

OK_UI_STYLE 0

in the DBWAPPUSER.PAR file will overwrite the user assigned value for that specific option.

With such extension, the DBWAPPUSER.PAR file (that must be kept read-only on each user’s sub-folder) can contain only the Options→User specific options that the Administrator likes to force.