Hmm.. just noodling around tonight. Question: >>I want the button to simply remove a workspace bookmark icon and recreate it<<
Are you recreating on a different server? Or pointing to a new application with a different replica ID?
I'm assuming that you are retiring one application for a newer version, and have created the new one with a different replica ID, then you can change the filename and replica id to match the old one on the server. This will not affect users, because their link will still be valid, and when they click on the icon, it will change to reflect the new graphic and name.
If this is so, then prepare in advance with your new copy on a local before you move it different folder on the server for deployment:
1. Make a new production copy to the target filename.
2. Change the replica ID to match the target database replica ID (http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24003943)
3. Down the server, and move the old database out of the data directory, and replace with the new one that you've modified.
----------
If you're moving the database to another server, then replicate it there, turn off replication on the old version along with template updates, and add an open page that redirects them to the new replica on the new server... Send an advance note out to users on how to remove the old replica from the stacked icons and set a time limit when you will no longer make the old replica available. (If the users have access to the new server, or at least one icon on their workspace from the new server, clicking on the icon pointing to an invalid server will prompt a search to the new server and Notes should automatically resolve and update the current workspace icon).
This tool will programmatically change every instance of a server name on desktop.dsk, including replication history. Caveat, it must be run locally on the client. We set it up the login script to run it when the users signed on to their computers and before Notes was active.
This has been a real annoying problem since lotus 4.0 No access to desktop.dsk/desktop.ndk I have used a solution that Duffbert came up with. When I used it we were in a 5.0 environment so I have not 6.5 tested it. it is not as pretty as you would like it to be and you have less control than is optimum.. But it is the best bad solution available
Are you recreating on a different server? Or pointing to a new application with a different replica ID?
I'm assuming that you are retiring one application for a newer version, and have created the new one with a different replica ID, then you can change the filename and replica id to match the old one on the server. This will not affect users, because their link will still be valid, and when they click on the icon, it will change to reflect the new graphic and name.
If this is so, then prepare in advance with your new copy on a local before you move it different folder on the server for deployment:
1. Make a new production copy to the target filename.
2. Change the replica ID to match the target database replica ID (http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg24003943)
3. Down the server, and move the old database out of the data directory, and replace with the new one that you've modified.
----------
If you're moving the database to another server, then replicate it there, turn off replication on the old version along with template updates, and add an open page that redirects them to the new replica on the new server... Send an advance note out to users on how to remove the old replica from the stacked icons and set a time limit when you will no longer make the old replica available. (If the users have access to the new server, or at least one icon on their workspace from the new server, clicking on the icon pointing to an invalid server will prompt a search to the new server and Notes should automatically resolve and update the current workspace icon).
---------
Last is a bit clunky, but I used it to migrate users in a domain name change.. Disktool: http://www-1.ibm.com/support/docview.wss?rs=0&q1=icons&uid=swg24004260&loc=en_US&cs=utf-8&cc=us&lang=en
This tool will programmatically change every instance of a server name on desktop.dsk, including replication history. Caveat, it must be run locally on the client. We set it up the login script to run it when the users signed on to their computers and before Notes was active.