SNTT: Stopping users from opening the wrong replica
Sean Cull 22 October 2008 22:00:00
One of the great strengths of notes is that users can access the same information on different servers or on local replicas. It can also be a real problem.
I have frequently had calls from people along the lines of
"I added some information and I can see it but my colleague can't".
One of our clients recently wanted to deploy replicas of their business critical applications to a different server to improve robustness. Without taking any special steps this actually reduces robustness and user satisfaction because over a period of time users end up using different replicas from each other and sometimes are using a slow server ( a branch office in South Africa on broadband was often a culprit ) without realising this.
The dynamics of how Notes chooses which server to open next often puzzles me but I was once told that it was to do with the alphabetical order of the servers because of the order of the databases in catalog.nsf - and once the top icon is for a distant server users will always use that server.
Anyhow, the code that follows may help. In this particular case the business applications are only used on one site so access to any off-site server should only be required if the on-site server cannot be accessed, his makes it easy - in other projects I have used a rule whereby the application should be accessed on the same server as the persons mail file
There are 3 design elements :
1) an action that creates a profile document listing the name of the preferred server - this is manually triggered when the system is set up
2) some script in the database initialize script which compares the preferred server lists above with the actual server
3) a subform which pops up to alert the user if looks as though they are using the wrong server.
Essentially the code does the following :
checks to see if the person has access to the database
gets the preferred server name from the profile document and compares this with the actual server name.
if the actual server != the preferred server then the system checks to see if the preferred server can be opened.
if the preferred server can be opened then the user is advised as shown in the screen shots below otherwise the user is allowed to open the requested server
I wasn't able to write code to actually switch to the new database so instead it closes the database and brings the correct icon to the top on the workspace. i have not tried this in a "workspaceless" environment.
You may think that the steps required to access the "wrong" server are a bit OTT but remember that this pop up only gets triggered when the "preferred" server is available.
Continue Reading "SNTT: Stopping users from opening the wrong replica" »
Admin Tips Dev Tips Show-n-Tell Thursday Download
- Comments [0]


Recent comments