The code chunk finally gets around to opening the database to be deployed and replicating it locally at lines 14 through 27. There's error checking to make sure that the user opened it successfully and then the databases is replicated locally. Note that the database is assumed to be in the same location on the user's Notes workstation as on the server.

Once you've got a local replica of the database you can then add that database to the NAMES= line of the NOTES.INI to cause it to be cascaded. This is performed in lines 28 through 39.

If this database was part of a larger application, you should repeat the local replication section of the script as often as necessary for all of the databases in the application suite.

That's it. One stop shopping for your Notes users and a problem solved for your Notes administrators. I hope that these articles have been helpful and that you've picked up some new ideas along the way. If there are other deployment issues that your organization has, write to me via at recheand@tacticatech.com. We could feature a solution to your problem in an upcoming article.

Richard Echeandia is senior technical editor of DominoPower magazine and a Principal with Tactica Technology Group in Dallas Texas. Tactica Technology Group is a Lotus Premium Business Partner offering Domino, Lotus Notes and Management consulting services to clients nationwide. He can be reached on-line at recheand@tacticatech.com.