Fatal Errors When Importing a Subfile


A fatal error detected during subfile import will halt the import process before any changes have been made to either the parent file or the subfile.


Many of these errors can only occur if unwise changes are made to the master file, because subfiles are prevented from making most types of changes that would result in fatal errors.


A fatal error will occur if:


1. Source File Not Recognized

The file being imported is not recognized as a subfile of the currently open file.


2. Multi-Level Import Attempted Prematurely

An attempt is made to import a low-level subfile into an ancestral file before all the intermediate single-level imports have occurred.


3. Parent Cost Item Deleted

The cost item in the parent file from which the subfile was originally exported no longer exists.


4. Sibling Overflow

Additional cost items have been added to the subfile family in the parent file so that sibling group overflow occurs when the subfile is imported. (This is more likely to occur with a fixed-digit numbering system where the sibling group limit is 9, than with a decimal system where the limit is 200.)


5. General Data Overflow

Additional general data fields have been added to both the parent or the subfile since the subfile was created, so that when the subfile is imported the limit for that field is exceeded. For example, Mandrel permits a total of 16 identification fields, so that if there were originally 10 identification fields when the subfile was created, and both parent and subfile have independently added 4 more each, overflow will occur on import.


6. Allocation System Deficit

A cost allocation system was set up in the master file, but the number of allocation blocks has since been reduced in the master file, so that some of the data in the subfile would be orphaned if it was imported.


7. Different Allocation Types

A cost allocation system was set up in the master file, but the type of its allocation blocks has since been changed, so that the subfile data no longer corresponds to the new allocation system. N.B. a calendar-based allocation system can be changed provided the block length is not changed. For example, the master file can change from calendar years to fiscal years without a problem, but not from calendar years to months.


8. Different Risk Matrix Sizes

The risk matrix size in the master file has been changed since the subfile was created. This will only cause a fatal error if there are any risk impact scales in the subfile. Changes to the risk matrix other than to its size will not cause a fatal error.


9. Price Definition Incompatibility

A price definition common to both subfile and master file has been changed in the master file so that it now has a different quantity unit or a different currency from the same price definition in the subfile. Changes to the unit price or the price name will not cause a fatal error.