In order to make offline changes for a local application, you must first stop your application, make the modifications or additions to Points.mdb, and then restart the application.
If you are working with a remote application, you stop the application on the primary configuration server, make the modifications or additions to the Points.mdb file, restart the application, and perform an update. Once the update has been completed, the tag changes will be propagated to all workstations running the application.
Note: Instructions on performing an update to a resource item are provided in Update Changes to Resource Items.
It is recommended that a maximum of 300 offline changes be made to tags at one time for a remote application; any more than 300 simultaneous changes will slow down the application startup process considerably. It is estimated that there is an initial hiatus of approximately 1 minute, and that 2 tags per second are processed. At present, VTS is configured to request locks on a one-by-one basis for each tag that has been changed but for which a lock was not already held. In the event that you have hundreds of tag modifications or additions, it is recommended that you complete them in 300 tag increments, following the instructions indicated above in the preceding paragraph.