Daniel tells me that this Class created more "support calls" than any other. He says:

Publicly posting the NotesUnreadMarksClass has generated more email from people with hassles than I ever could have imagined. The implementation of Unread Marks within the Notes client changes constantly from version to version. Needless to say that the class would never work from the UI, something that I keep telling people, but they don't seem to listen. On a positive note, I had heard from one person who managed to use the UnreadMarks class to implement Unread Marks on a Web interface. I would hate to see the code behind that.

Maybe if this person is reading this article, he might care to share this experience and his code with us on the Powerboards or in an article.

DBDesign
This class gives you access to Notes design notes as NotesDocuments. Being written by an Iris insider, Damien Katz, I guess it comes with the extra value of that Iris knowledge. It was originally written in 1999, in the early days of R5, so I would think--I've not tested it--that it doesn't work with the new design elements in RNext. There are actually two versions of this on the Sandbox. The original was posted on August 25, 1999 and can be easily found by using "DatabaseDesign" as a search term. Get this version, because it has Damien's documentation. A later version, modified by Notes.Net reader Aaron Oneal, is also present. This one can be found with a search term of "DBDesign." It's Damien's original code with the addition of an extra method that enables you to compile Lotuscript. The intention of this change was to enable you to force recompiling of Script libraries and to be in control of the order that this happens. Pity that in creating it the documentation was lost, so if you need the updated version, also download the original so that you have the documentation.

The class enables you to probe the design documents in detail. Doing this does require that you have an understanding of how Notes design documents work. The available documentation describes the class properties and methods, but it doesn't explain the field values on the design documents. You really need to read the code and the comments in the script library in detail, because this is the only way that you can find all this stuff out. Table A will help you to get started; it calls out the most useful fields and explains them.