Internal Mapping Files

The application relies on several internal mapping files. These define where external mapping files are located on your system network, or they define the mapping of strings or attributes between the base product and the intermediate file. It is your responsibility to modify them correctly so that they indicate the correct file location.

Note:

If you change any of the internal mapping files, you must reload the base product's user application from macros. Alternatively you can use the Re-initialize menu option on the main Import and Export forms, you should then resave the binary UI.

Internal mapping files are loaded on start-up of the application. If there are any problems on loading, you will be prompted to confirm that you want to carry on with using the application, although it is frequently inadvisable. If you do not continue, a fatal error is raised and the application exited.

Internal mapping files must have a suffix '.map' and be stored in one of 3 areas pointed to by the environment variables for the system default area, the project defaults, for example: SAMDFLTS, and your work area. In locating the map files, the folders are searched in the listed sequence. This enables you to have company, project and user mapping files that can overload the previously installed versions. The example internal files supplied by the system should be found in the folder, BocadMaps.

Internal mapping files are of the form of an asterisk (*) separated sequence of strings. The first line of the file is taken to be a file identifier, the precise rules for which are defined below.

As an aid to generalising your application, you may include environment variables in the path names as long as they are defined in the base product format; for example:

%ENVVAR%\¼

These environment variables cannot be search paths: they must translate to a reference to a single folder.