Convert Database to Current Version
Converts entire database, class table or individual files to the current version of Adams.
For the option: | Do the following: |
|---|---|
Database | Select the database which contains the files to be converted. |
Convert | Select the scope of the conversion, entire database, class table or single file. |
If class table is selected, the following options become available: | |
Class | Select the class (database table) to be converted. |
Table Info | Select to show the list of cdb tables defined in the configuration files. |
If Single File selected, the following options available: | |
Class | Select the class (database table) of the file to be converted. |
Filename | Select the property file which you want to convert. |
 | Select to view property file information. By default, your template-based product displays this information in the Information window, but you can choose to display the information in a text editor. Learn about: |
 | Select to modify: While Curve Manager is active, you cannot perform operations in the main window. After exiting the tool, you can resume working in the main window. |
Target Folder | Review the folder for the new target database to be created. If the selected source database is writable, the field will show its parent folder, otherwise the current working directory. Selecting this option will allow overwriting the suggested defaults. |
 | Select to open the file browser to select (or optionally create) an alternative target database storage folder |
Convert assembly format | When converting an entire database, assembly table or individual assembly file, selecting this option will ignore the file format of the source file, and use the selected format instead: ■TeimOrbit - Saves the file in human-readable character format. ■XML - Saves the file in the Extensible Markup Language format. |
Convert subsystem format | When converting an entire database, subsystem table or individual subsystem file, selecting this option will ignore the file format of the source file, and use the selected format instead: ■TeimOrbit - Saves the file in human-readable character format. ■XML - Saves the file in the Extensible Markup Language format. |
Convert template format | When converting an entire database, template table or individual template file, selecting this option will ignore the file format of the source file, and use the selected format instead: ■Ascii - Saves the file in human-readable character format (TeimOrbit). ■Binary - Saves the file in binary format (platform-independent). ■EDS - Saves the file in a platform-independent enhanced dataset format. |
Convert property file(s) from TeimOrbit to XML | When converting property files that are supported in both, TeimOrbit and XML format, selecting this option will ignore the file format of the source file, and convert TeimOrbit files to XML. Currently supported property files classes for XML conversion are: ■spring (including linear spring and air-spring) ■damper (including linear damper) ■bushing (including linear bushing) ■bumpstop ■reboundstop ■driver controls |
Repair hardpoint locations | Only enabled if the user has specified a custom coordinate system in their cfg file. When converting an entire database, subsystem table or individual subsystem file, selecting this option will repair hardpoint locations. |
Database Info | Select to display a list of the search directories, including their search level, database name, and database path. |
Notes: | Please use the assembly, subsystem, and property file format conversion options with caution! Using those options will not only change the file format, but also the file extensions. Other files referencing the format converted files may no longer work, for example ■Property file references in subsystem files ■Subsystem file references in Assembly files ■Assembly file references in Event Set files If format conversion is chosen for the above file types, the higher order files referencing them need to be hand-edited to resolve issues caused by the file extension changes. Template format changes are unproblematic because all file formats use the same extension (*.tpl). |