That is why when opening this RTD in 'Repair Mode' these job preferences will be still used.

Step a/ results in saving job preferences of the original RTD file as default job preferences. The steps to perform to avoid such effects when using 'Repair Mode'are as follows:Ī/ opening the original model without 'Repair Mode', opening Job Preferences and using 'Save current parameters as default':ī/ starting a new project and opening the original model with 'Repair Mode'Ĭ/ using Save As or Save (Save As recommended) So in practice opening the same *(Recovered).RTD file on 5 different machines with different default job preferences it is possible to obtain 5 different sets of codes active (and different from the original ones). !!! After using Save or Save As command these 'new' job preferences are saved inside the file replacing the original ones.ģ/ When sending RTD file created in step 1/ and opening it on another machine it will 'use' the default job preferences of this another machine because it has no job preferences inside. The file with '(Recovered)' in its name, created by default (without any Save or Save As command) after opening in 'Repair Mode' has no such information inside.Ģ/ That is why such file is opened with default job preferences which can be completely different than its original job preferences - different units, codes, analysis settings. Open in 'Repair Mode' should be used in case of damaged RTD or if its size is abnormally big because of many edit/delete operations and discontinuous internal structure.īut when using this type of open it is important to remember/know about some topics to avoid 'damaging' instead of 'correcting':ġ/ The first point is that opening in 'Repair Mode' removes from the model its Job Preferences and its properties (like the information in which version it was created).

I hope this information will explain some unexpected effects observed when opening in 'Repair Mode'

Endnote com exception has occurred