If the dialog at the beginning of the import claims for unknown DDTs, search for local type declarations in this DDT and find out which of these are undefined.

Further, types unused but present in the opened *.asc file are reported as unknown in a dialog during import.

This happens for Concept system data types, which are considered for Concept to be always presented and therefore not included in the export by Concept.

The Converter automatically includes the standard system data types of Concept individually, if they are needed. They are part of the converter command and include file CConv.xml present in the execution directory of Control Expert.

If the read-only-flag is removed, this file can be extended to include additional data types for user EFB libraries.

Such data type files beyond the global/local ones are placed in the lib subdirectory of Concept to be merged into the Concept application, but these data types do NOT appear in the Concept export file.

The V1.1 version of the Concept converter will have the capability to add Concept *.dty files, which are stored in the same directory as the *.asc file, to the converted application, as if their content were appearing inside the *.asc file itself.