Create Tabs Where the ComesAfter Attribute of the Tabs Refers to the Same Tab

In our example, tabs are created in each file with the ComesAfter attribute, and each instance of the attribute refers to the same tab. 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), and both have ComesAfter="Input" (that is, both come after the Input tab)).

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

   This file contains an Averages tab with ComesAfter="Input" (that is, it comes after the Input 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:

• Main

• Input

• Averages

• Alarming

• Alarming Limit

The farms\farms.xml file has two tabs defined: the Main tab at the beginning of the file, and the Input tab at the end of the file.

The zz_farms\farms.Alter.xml file contains the Averages tab.

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.

If you rename the zz_farms folder to aa_farms, the tabs order of the tabs from left to right is as follows:

• Main

• Input

• Alarming

• Alarming Limit

• Averages