Here is a standard variable setup to maintain a corporate standard interface in MicroStation SE.
_ustn_userint=<pathname>
_ustn_userintname=<username>
%lock_ustn_userintname
_ustn_uipath=<path1>;<path2>;<path3>
%lock_ustn_uipath
Variable descriptions:
_ustn_userint=<pathnname to Parent directory>
_ustn_userintname=<user interface name>
These two variables tell MicroStation SE which m01 file to write. The userint variable should be the path to the parent directory that contains all of your interfaces. The userintname variable is the name of the directory that contains the m01 files.
%lock_ustn_userintname
This locks the userintname variable, so the user cannot change it. Every time they enter MicroStation SE, the user will be in the same interface.
_ustn_uipath= <path1>;<path2>;<path3>
This variable tells MicroStation SE which m01 files to read. The corporate standard m01 file should be last. This insures that the standard interface will be the last interface read, and the user will have all the standard modifications.
<%lock_ustn_uipath>
Locks the uipath variable.
Example
I have my directory structure set up as shown below. I have a directory called c:\win32app\ms\interfaces\, which is the parent directory for my interface files. Under this directory are the following subdirectories: user, project and standard. Each of these subdirectories contains my m01 files for that particular interface. The ..\user directory is for modifications that the user makes, the ..\standards directory is for corporate standards, and the ..\project would be any miscellaneous interface you also load.
_ustn_userint=c:\win32app\ms\interfaces\
_ustn_userintname=user
%lock_ustn_userintname
_ustn_uipath=c:\win32app\ms\interfaces\user
\;c:\win32app\interfaces\project\;c:\win32app\interfaces\standard\
%lock_ustn_uipath
Using this method you can choose which m01 file the user writes, and which m01 file is loaded last. In this case, the ..\user interface is loaded first, then the project, then the standard. The ..\user interface will contain modifications the user wishes to make. Setting the files in the ..\user directory read-only will prevent the user from making modifications.