Macros File-based Design Import

The FBDI process of one V5 document can lead to two V6 PLM macros libraries. One containing the macros written in catscript and one for the macros written in vbscript (only these two kinds of program can be embedded in a V5 document).

Of course, the FBDI process of a V5 document with no macros does not generate any V6 PLM macro libraries.

The FBDI process is successful when there is no macro contained in the V5 document with a forbidden letter in its name. A forbidden letter is a letter that is not allowed for windows file (slash, antislash, etc). When the Macro contains special characters, only the Part is imported and not the Macro.

Because the V5 automation model is not compliant with the V6 one, most of V5 macros cannot be used "As Is" in V6. To prevent problems, the FBDI process adds a string at the beginning of all V6 macros to make them non-executable.

Important: The macro library name in V6 contains the document name in V5. The nomenclature in V6 is defined as follows: <Version 5 document name>_<prefix entered in the creation preferences dialog box><session identifier>< VBScript>.

For more information, refer to the following topics:

• Running FBDI Interactively
• Importing Application Files from Previous Versions