Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Assuming that you do not require the documents in the view to be hidden. Ben's response is quite good. But I am not a big fan of Reader lists in view designs, even if you're using ACL roles to manage them. Reader view lists are notoriously hard to maintain, and easily overlooked later when debugging user issues.</p> <p>If you want to prevent UI access to the view but still permit the user access to the documents via the application programmatically, you will need to goto the view's "QueryOpen" event in the Domino Designer and insert the the following code.</p> <pre><code>Sub Queryopen(Source As Notesuiview, Continue As Variant) messageBox "Not authorised to access this view" Continue = false End Sub </code></pre> <p>This should prevent a user opening the view via the UI as you described, but allow the application to use it where required. And if so desired later on, you can programmatically control when those views can be access by the UI. I have had a couple of instances where I have had to create control objects that determine which type of user can open/paste documents into a view.</p> <p>My answer is on the basis you just want to prevent people accessing views. But if you need to actually hide the documents in the view, then you need to consider document level security, and then design your application around that. Admittedly, this will increase the complexity of the application because, if required, you'll need to use agents to run on someone else's behalf in order to act on the documents the user can't see. </p>
    singulars
    1. This table or related slice is empty.
    1. POSecuring Hidden Views in Lotus Notes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgiulio
    1. USgiulio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSecuring Hidden Views in Lotus Notes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COGood answer giulio!
      singulars
      1. PO
      1. USKen Pespisa
    2. COYou can refine the QueryOpen check with a role check too, so that [DBAdmin] users can access the view or prompt for a password to access the view. A simple hard-coded password is often sufficient but feel free to try whatever suits you. That way essential support access is possible.
      singulars
      1. PO
      1. USandora
    3. COOnce you're exploiting the queryopen event you can define what ever logic you require. In previous projects, I have defined an access sub-system where an admin could turn on/off querypaste/queryopen of views dynamically.
      singulars
      1. PO
      1. USgiulio
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload