Managing M/SQL Components


VC/m includes 2 sets of component drivers for M/SQL components. These correspond to the two types of import and export functions built into M/SQL.

The first set (whose names begin with M) use the ^mxdd import and export functions to transfer the components. These externalize all the definitions.

The second set (whose names begin with C) use the old M/SQL import and export functions to transfer the M/SQL components. These do a more physical copy of the M/SQL globals.

The main difference between the two is that the second set preserve the RowIds of the tables and forms. These drivers should be used when hard-coded references to RowIds have been used in the code. The first set are preferred in other cases, particularly if development is doing done in more than one place.

For each location where the M/SQL components can be run, configure the location definition so that these components have a storage format of "M" and a physical address of the namespace or directory where they should be placed.

If the first set of component drivers are used, the following global node must be set, depending on the version of FDBMS which is being used. For version 14.x or lower:

set ^%vcvc("msql_version")="F14"

For version 15 or higher:

set ^%vcvc("msql_version")="F15"