Automatic Communication

Once a branch office has been initialized using a data stock download, the branch office can communicate with the main office automatically.

To use automatic communication without manual match-up requires:

• Always use the COM user to prevent concurrent communication sessions from overwriting data.

  If you use the SU for automatic communication, you need to use the option q (mmco.exe -u su -p <Password> -k o,q ), see mmco.exe Parameters. Otherwise you are prompted to register your license and the communication process is canceled.

• Use communication formats that require no user interaction:
  • Disable Change control, see Field Properties.
  • If you have customized the match-up behavior (default is match up by primary key, see Match-up), you need to enable the No manual control for each match-up line you define for the line to be applied, see Match-Up Control. Use match-up settings that log similar records, see Automatic Communication with SIM Files.
  Note: Use the m and k parameters to communicate automatically with manual control. Messages are output, changes can be verified manually and records can be matched up manually, see Communication with Change Control and Communication with Manual Match-up.
• Select Automatic or Manual/ Autom . as the Execution type (Communication info area) in communication connections that should support automatic communication, see Defining Communication Connections.
• Start automatic communication sessions from the command line, see mmco.exe Parameters and Automatic Communication Examples.

  Use batch files that start mmco.exe with the desired parameters and transfer communication files to where they can be accessed by the target station.

• Use time-controlled software (e.g. Windows' Task Planner) to start communication automatically.
• You can automate the transfer of communication files with update.transfer 2.0.