Super projects > General advice

In this section, you will find some practical advice regarding super projects and how to work with them.

•Do not create many small sub-projects. Keep the number of sub-projects as low as possible.

•Divide the documentation into sub-projects in such a way that the number of references between the sub-projects is kept as low as possible.

•The file name composition should be setup in such a way that all file names in the entire super project are unique. Even if that currently is not a strict limitation, the advantages of complying with that rule are vast, and future updates with upgraded functionality and performance may require that anyway.

•The composition of cross-references should be made in such a way that cross-references are unambiguous within the entire super project.

•You may contact cadett’s support to get personal advice on how to make a customized con-figuration optimized for your specific needs.

•When working with cadett ELSA, you may sometimes run into issues where the content of the drawing sheets does not match the content of the OnLine database. That might result in strange behaviour, like so-called “ghost errors”. The simple solution to that is always to regenerate the OnLine database, which is done with a couple of mouse clicks. Not a big deal, in other words.

However, in super projects it is not always that easy. A regeneration of the OnLine data-base in a sub-project only affects that sub-project. Any errors from other sub-projects, or in the super project database that connects all sub-projects with each other, will not be fixed. To make sure that all such errors are eliminated, the OnLine databases of all sub-projects must be regenerated, after which the super project database is regenerated, and finally the drawing sheets updated from that. In cadett ELSA Professional, it is possible to perform that process manually, but that may be a tiresome task, which is not always appreciated. In cadett ELSA Enterprise however, a feature is available that automatically performs the entire process using one single command. Please refer to the Report generator chapter of the Reference Manual for a complete documentation of that feature.