Download MDE User Manual

M Data Extractor
User Manual
If determined to be a new installation of MDE, naming convention C will be set as the default.
Table 17:
Naming Convention
MDE Version
A
All versions up to 2.3.0
B
Version 2.3.0 only
C
Versions 2.3.1 and higher
Note: The naming convention for MDE 3.0 is specific to the Client installation of MDE. If
multiple clients are installed at your site, please make sure that all are using the same
naming convention.
Why support multiple naming conventions:
As the user group for the MDE expanded, users began report issues with the way the tables and
fields names for the target database were created. The naming convention changes as they
apply to A, B and C are defined below:
Table 18:
Naming Convention
Issues Resolved
A
Naming convention A uses the original
structure in creating table and field names
B
More than one FileMan field can have the same name for
a given file for a give Multiple level. Though most FileMan fields have different alphanumeric names, there is
no requirement that the names be unique, only that the
corresponding field number be unique. The original versions of the MDE were displaying on the first of any identical field names. Starting with 2.3.0, the field number
was appended onto the end of each field name.
C
In order to address relational table names that could be
identical, the MDE started appending all table names
(and any names of fields comprising nested files or multiples) with the unique FileMan name. If a given table
name is part of a FileMan multiple, then each naming
component would also be appended with its own unique
field number.
Starting with second-level multiples, the names were
shortened to the first letter, followed by an underscore,
followed by the unique FileMan number.
Numbers having decimal points now have the decimal
point replaced with ‘#’ and the ‘#’ character is no longer
used to indicate an ellipsis mark.
Appendix - 6
Strategic Reporting Systems, Inc.