Don't get locked out by your own readers field

This trick keeps your field from locking you out, but use with caution.

Ever accidentally set the wrong value in a Readers field and lose the document to the depts of notes security? Here's a little trick to make sure you'll never lose another document again.

Firstly create the role in your Db's ACL, 'SuperUser'.

On your form create two fields:
1. ReadersEdit - set as an editable keyword field using the ACL for choices, allow multi-values (or choose appropriate method of populating for yourself).

2. Readers - set as a computed Readers field with the following formula:
"[SuperUser]" : ReadersEdit

Any changes you wish to make to your readers field will have to be made through ReadersEdit. It functions the exact same as a normal readers field, except that anyone with the role 'SuperUser' will always be able to read/ access the documents in your db. Remember, this is a back-door to your security so be selective on who you give the superUser role to!

This was first published in November 2001

Dig Deeper



Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:




  • iSeries tutorials's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...