Exporting Data from Your Database

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.4.
This help file does not exist in MainBoss 4.2.4, but the index for that version can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

The Export verb of MBUtility exports selected data from your database to an output file. For example, you might regularly wish to export data to another application for some reason; by making a command file that uses MBUtility, you could automate the export process, thereby simplifying the task (and also avoiding errors).

The command line for exporting is

mbutility Export option option ...

where the options are:

/SchemaIdentification:schema

Specifies a data schema for exporting the data. This should be one of MBUtility's built-in schemas (as discussed in Built-In Data Schemas). If the schema name contains blank characters, the name should be enclosed in quotes, as in

/si:"Storeroom Assignment"

/+EmbeddedSchema

Tells MBUtility to embed the specified data schema in the output file. This is useful if you're exporting the data to software that accepts embedded schemas. However, Microsoft Excel doesn't seem to accept such schemas, so don't use +es for going to Excel.

/-EmbeddedSchema

Tells MBUtility not to embed a data schema in the output file. This is the default.

/Output:filename

Specifies a file where the output should be written. This file will be written in Unicode characters, which means it should only be edited with software that can deal with Unicode (e.g. Wordpad).

/OrganizationName:name

The name of the maintenance organization (associated with your MainBoss database). This name is case-insensitive; for example, MainBoss is the same as mainboss.

/DataBaseServer:servername

The name of the server that holds the MainBoss database.

/DataBaseName:name

The name of the MainBoss database.

If you specify /OrganizationName, you don't have to specify either /DataBaseServer or /DataBaseName. If you don't specify /OrganizationName, you must specify both /DataBaseServer and /DataBaseName.

For example,

mbutility ex /si:Unit /out:myunits /on:MyMainBoss +es

exports data about units to a file named myunits. The output file will include an embedded data schema for unit records.

< Previous section  |  Table of Contents  |  Index  |  Next section >