MSM-Workstation
Format of "Export" Files

Definitions of windows can be copied between databases by means of the "import/export" facility on the "File" menu.

The "export" facility creates a file ("xxxxxxxx.VEX") that can be interpreted by MSM-Workstation in order to re-create the definition of the entities contained in the export file.

The format of these export files is very similar to the format of the export files created by Microsoft's Visual BasicTM (as an example, two files are included with this documentation, one containing two very simple windows and one containing all supported components):

header
property        =   value
...
Begin [entity] [name] [object type]
   property        =   value
   ...
   Begin [sub-entity] [name] [object type]
      property        =   value
      ...
      Begin [sub-sub-entity] [name] [object type]
         property        =   value
         ...
      End
   End
End
Begin [entity] [name] [object type]
   property        =   value
   ...
   Begin [sub-entity] [name] [object type]
      property        =   value
      ...
      Begin [sub-sub-entity] [name] [object type]
         property        =   value
         ...
      End
   End
End
For MSM-Workstation, the header of an export file looks like: 
MSM-ViEW
Product         =   Builder
ProductVersion  =   2.0.0
Format          =   Export
FormatVersion   =   1.1
Workshop        =   EDM,EDM
Workbench       =   1901042;875917314
Date            =   14 OCT 97
Time            =    1:43 PM
The definition of a window follows the pattern: 
Begin [entity] [name] [object type]
   property        =   value
   ...
   Begin [sub-entity] [name] [object type]
      property        =   value
      ...
      Begin [sub-sub-entity] [name] [object type]
         property        =   value
         ...
      End
   End
End
where [entity] is equal to window, [name] is the name of the window in question and [object type] is equal to GUI.MSM.

For a window, a [sub-entity] may be a Control, or a Menu, or a ToolBar, or action logic to handle a specific event. Further details depend on the kind of "control" (also called "gadget" and "component") being defined.

Below, the properties and sub-entities for the various components are described in more detail.

Window, Menu, ToolBar, Choice, Button, CheckBox, Combo, Date, Document, DropCombo, DropDown, Generic, GroupBox, Label, ListBox, LongList, Picture, RadioButton, Scroll, SpinButton, TabbedGroup, TextBox and Timer.