Common Import Behavior
Considerations
You should take the following considerations into account:
- DBDI Process
-
The DBDI process of a V5 document with no macros does not generate any 3DEXPERIENCE PLM macro libraries.
The DBDI 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 3DEXPERIENCE one, most of V5 macros cannot be used "As Is" in 3DEXPERIENCE. To prevent problems, the DBDI process adds a string at the beginning of all 3DEXPERIENCE macros to make them non-executable.
Important: The macro library name in 3DEXPERIENCE contains the document name in V5. The nomenclature in 3DEXPERIENCE is defined as follows: <Version 5 document name>_<prefix entered in the creation preferences dialog box><session identifier>< VBScript>.