1. Run the VTS application or the OEM layer application (depending on where you wish to add the new tag type). Note: If you are adding the new tag type to an OEM layer, and it does not have a server specified, set its server to match the application layer's server (using the Application Properties dialog).
2. If the code for the new tag type has already been compiled and tested, move it into the running layer's directory; otherwise, create an empty module source file that you know will compile:
Main [
]
3. Perform an Update All operation from the Remote Configuration dialog; the new file is added to the list.
4. Lock the AppMod.src file, and if the new tag type's code has not already been tested (i.e. you created the empty module file in step 2), lock the source code file as well.
5. Stop the running layer.
6. If you locked the source file in step 4, create the new tag type code in that source file now; otherwise, skip to step 7.
7. Add the module declaration for the new tag type in the POINTS section of the AppMod.src root file.
8. Compile the layer and fix any compiler errors.
9. In the application layer's application directory (regardless of the layer to which the tag type has been added), create the tag table in Points.mdb. Do not edit SCT.mdb. Note: If you are using Office 2000, you will have to convert the Points.mdb file to Office 2000 format before you can add a new table.
10. Open the Application Properties dialog for the application layer and select the Force Clients to Resynchronize: Tags checkbox. All OEM layers will also have their Force Clients to Resynchronize: Tags checkboxes selected as a result. All clients will be requested to restart at this point, but don't restart them yet.
11. Start the layer where the new tag type code was added and do an Update Item on AppMod.src. (Assuming you didn't make any changes to the source code after the application was compiled (i.e. the files are in-sync), the server will not be requested to restart).
12. If you locked the source file in step 4, do an Update Item on the new tag type's file.
13. If the OEM layer is the one running, stop it and start the application layer.
14. Restart all clients. Note that the clients' Points.mdb file will contain the new tag type table, but the SCT.mdb file will not have the new table until a tag of that type has been created and updated.