Bizaare view behaviour - opening view in seperate database

HCL Domino Domino Forum
1

Ok…

This is a strange one. I have a view in a database. It sits on a outline, called the ‘main’ outline, and its set to open a view via ‘Named Element’ ‘View’ ‘Administration\ReadyToPay’.

It is designed with a Frameset, and I have set the view to open in the ‘Right’ frame (just like other views).

The view (just like other views) has no ‘inherit from template’ set (this is normal), the database does inherit it’s design from a production template called MatchException.

When clicking on this particular view, for some bizaare reason, it opens a completely seperate database, on a completely seperate server.

The database it opens is very similar to the production one (its a QA version of it!), but has a different replica ID, a different template to inherit it’s design from, and is, to all intents and purposes, a totally seperate database on a totally seperate server…

How come the PRODUCTIOn database opens a view on a QA database, on a seperate server, different repID, different template ??? The view seems to exist in production, but is not being opened when you click on the navigator ???

Any ideas???

Cheers

Generic…

2

Subject: RE: Bizaare view behaviour - opening view in seperate database

The Notes client has no way to know which databases you consider “Production” versus “QA.” The outline entry was created by someone who had the QA version of the database in their Notes workspace, and they selected that database to create the link. The replica ID of that QA database is therefore recorded in the outline design.

You can edit the outline design in the production application and change it to refer to the correct production database. Or you can use a formula instead of a link, and express in macro language the rule that checks which version of the database you’re in and opens the appropriate other database – that way the application will work in both environments.