I seem to remember… that if you clicked on an icon for a database, and it no longer existed on that server… that somehow it knew (?) to open a replica if it could find one. Do I remember incorrectly? Cuz now, when I click on the icon, i just get the dialog box that has a drop down to pick another server from… what if I don’t want the user’s to have to do that and I have moved a database to another server… is there a more seamless way to get the other DB (replica) to open?
Oh… and in case it matters… the OLD server is an R5 server (5.09 i think) and the new one is Dom6
Subject: is this a DB or server setting?
No, it won’t necessarily open another replica. I think it might if another replica has already been opened on that computer, but not sure that that’s always true. There are suggestions on the Notes 4/5 forum for what to do when you’ve moved a database.
Subject: Thanks, I’ll look there too
Subject: is this a DB or server setting?
Seems to me that’s what it would do if the server wasn’t responding – it would go to the first (alphabetically speaking) server that the user had access to that had a replica of the database on it. (One of our local offices in Toronto had a notoriously bad network. Their home Domino server was low man on the alphabetic totem pole. Users were continually being redirected to Vancouver – 4500 km away over a skinny WAN – and complaining about how slow Notes was.) Removing the db from the server might not automate things, but turning it off (while maintaining the server doc in the NAB) might. Problem is, you’ll wind up with server names like Aardvark and Aaaaalvin trying to control replica migration for different user groups.
Subject: RE: is this a DB or server setting?
Turning what off Stan, the database or the server?
We will eventually turn it off… but during this time it’ll be on a while… I did have one good suggestion from another thread… I can create a setup profile, and add a link to that database in the setup profile… then it should add it to their workspace… i’ll have to test that… but it sounds good!
Stan… are you following me?
Subject: RE: is this a DB or server setting?
Whither thou goest, there shall I go… ;o)
(Oh, and I did mean the server, BTW.)
Subject: is this a DB or server setting?
Keep the old database where it was (shut off replication first, but it does need to be a replica)and write a database open script to redirect them where you want them to go (Resources ==>>Other==>Database Script).
Subject: RE: is this a DB or server setting?
Thanks, but that would only work for so long… as the old server will be taken down and rebuilt… so I was looking for a way to eliminate confusion.
Subject: RE: is this a DB or server setting?
the only way it will automaticcaly roll over to the other replica is if it is already on the desktop as an icon.
I think your safest bet would be to send out a button to all of the users and ask them to click it (explain why to them of course) and include this code in the button:
@Command([AddDatabase]; “server”:“path”;“1”);
@Command([FileOpenDatabase]; “server”:“path”)
This will eliminate the dialog (but of course it will not remove the old icon)
Subject: RE: is this a DB or server setting?
Well now you are getting back to my original question… the user’s DO have an icon to the db on their workspace that points to the OLD server… it’s just that it doesnt’ automatically open to the new server. I think maybe my solution will be setup profiles… if I can get them to work the same as they did in R5 . Have to read how these Policy things change things.
thanks