Notes Client: Is ist possible to disable programmatically the View/Goto Option?

Hi there,

is there any way to disable in the menu the View/Goto option ? I want to limit access to a view, but due to preformance issues without using reader fields. Everything in the DB works quite well, but there is one huge hole:

In the application is an embedded and categorised view which is intended to be used by the user but only for his category(@user) . But he can go on the menu point VIEW and select GOTO and then select this view again and then the view opens and shows all categories .... Even a Continue=false in the QueryOpenDocument and a Source.Close or a UIDatabase.close is simply ignored by Notes if opened this way. Event tried to open a page instead - nada, zero, nix

Yep, also tried to use @SetViewInfo ... but this does not work in a Frameset with an embedded view ...

Any ideas ? TIA

Sincerly

Jochen "Joe" Herrmann

Hidden views (view name in paranthesis) are not shown on View- Goto menu.

(But is shown if you shift-ctrl-rightclick on the icon and select Application - Goto)

Real security comes with a cost...

You could close the UIView in the PostOpen event handler. But even then: Debugger - Stop an the view is still open.

I expect, you've already hidden the view by enclosing its name with (). But then there is pressing Ctrl-Shift while View\Goto showing the hidden views.

My opinion: Use readers/author fields.

In combination with the UserNotesName category the performance penalty is minor. The problem with reader fields normally is: The server has to iterate through lots and lots of documents, until he has collected "enough" to sent them to the Notes client. With the UserNotesName category, it only iterates through documents, the user is allowed to open - thus no performance loss.

Hello Thomas,

thanks for your reply. Yes the (NotesViewName) is not really a secure way ...

Will try the reader fields now, but my plan B is:

I will create 2 different communicating DB's . One for the user (employees) and one for the departement allowed to process the user input. But, the drawback is that I always have to synchronise both DB, so that the user can see the progress of the workflow and the processing departement the new user input.

Thanks guys.

Sincerly

Jochen "Joe" Herrmann