Create tabs without the ComesAfter attribute

In our example, tabs are created in each file without the ComesAfter attribute. When you execute the DBEditDisplaySchemaMerge command, DBEditDisplaySchemaMerge processes the tabs in the following order:

Note: farms is used as both the <component> and <table> name.

1. %DNADataRoot%\ADE\config\ADE\DBEdit\Schema\baseline\farms\farms.xml

   This file contains two tabs: Main and Input.

2. %DNADataRoot%\ADE\config\ADE\DBEdit\Schema\custom\farms\farms.Alter.xml

   This file contains two tabs: Alarming Limit and Alarming.

3. %DNADataRoot%\ADE\config\ADE\DBEdit\Schema\custom\zz_farms\farms.Alter.xml

   This file contains an Averages tab.

4. Execute the DBEditDisplaySchemaMerge command (refer to Merge all DBEdit XML files).

When DBEditDisplaySchemaMerge finishes compiling, and you open the farms form, the order of the tabs from left to right is as follows:

• Averages

• Alarming

• Alarming Limit

• Main

• Input

As mentioned in Understand the ordering of DBEditdisplaySchemaMerge and XML file naming conventions, DBEditDisplaySchemaMerge processes <table>.Alter.xml files in consecutive order. However, the Advanced Database Editor (ADE) displays the elements in reverse order if the ComesAfter attribute is not used.

The farms\farms.Alter.xml file has two tabs defined: the Alarming Limit tab at the beginning of the file, and the Alarming tab at the end of the file. After DBEditDisplaySchemaMerge finishes compiling, the Alarming tab comes before the Alarming Limit tab on the form.

The zz_farms\farms.xml file, which contains an Averages tab, is processed last by DBEditDisplaySchemaMerge. Despite being last in line, the Averages tab appears first in the form. This illustrates that, when you do not use the ComesAfter attribute, the last file processed by DBEditDisplaySchemaMerge will display first. Tabs in the other Alter.xml files will display in reverse order.