What is the $Reader field in lotus notes ? what it contains and what is the use?

HCL Domino Domino Forum
1

please answer …1)what is the $Reader field in lotus notes ? what it contains and what is the use?

  1. what is the major deference between Replace design and Refresh Design?

  2. what $Conflict field contains ? what is value in side that field ?

2

Subject: what is the $Reader field in lotus notes ? what it contains and what is the use?

Are you asking because you have a test on the subject? Those all seem like fairly straightforward things to find out, but hardly seem connected together. Search a bit in here and in the Help db for the answers (I’m not giving them if it might be a test).

3

Subject: RE: what is the $Reader field in lotus notes ? what it contains and what is the use?

I m having some confusion in these concepts …

4

Subject: RE: what is the $Reader field in lotus notes ? what it contains and what is the use?

Use designer help- they are all quite well described.

5

Subject: what is the $Reader field in lotus notes ? what it contains and what is the use?

  1. The first thing you need to know is that there is nothing special at all about the name “$Reader”. It is the TYPE of an item that matters, not the name. An item is the unit of data that is stored for a field on a form. (The difference between a field and item is not usually important, but it can be.) In Domino Designer, you can define fields with the type “Readers”. The actual item is stored as a SUMMARY READ ACCESS NAMES item. A lot of documentation simply refers to “Reader Names” fields. Some built-in features of the Notes client use the name $Readers for SUMMARY READ ACCESS NAMES items. Most developers use different names for their own fields in order to avoid conflicting with these features. In any case, an item of type SUMMARY READ ACCESS NAMES provides an extra layer of security for a Notes document. Any document that contains one or more items of this type (regardless of the item names!) can only be opened by users or servers whose names are listed in the item data – either directly, or through a group or role entry. Names that are listed directly must be in the proper "canonical’ format, otherwise they won’t work. In fact, the document will be invisible to all other users who are not listed, with one exception: administrators with Full Access rights can see and open documents regardless of the contents of their Reader Names items. An item called “$Reader” will behave this way if the item type is indeed SUMMARY READ ACCESS NAMES. If not, it will not do anything special at all.

2 & 3 I’ll leave for someone else.