Archives for the ‘Lotus Notes Client’ Category

10 Dec 2015

Notes Database Performance Tip: Disable Unread Marks

A Quick Summary of this Post

Unread Marks are enabled by default when creating a new Notes Database. In most cases, especially for applications used by multiple users, unread marks are not required and has a significant performance cost when the Notes database grows in size.

To disable Unread Marks:

  1. Right-click on your Notes database and select “Application -> Properties
  2. Click on the last tab
  3. Check the option “Don’t Maintain Unread Marks
  4. Compact the Notes database

A Detailed Overview

Through my years as a Notes developer, I’ve seem many cases where unread marks are enabled for Notes applications. One of the main reasons for this is that unread marks are by default enabled when creating a new Notes database. Many developers ignore this setting and continue developing an application for their client, where unread marks are most of the time not required.

Unfortunately, this comes at quite a cost to performance when the application grows in data, especially if the affected Notes database contains many Views.

In all my time as a Notes developer, I’ve never once required unread marks in the applications I developed. This became even more so the case when I moved to XPages development. I do understand that there are some cases where one would use it, but my recommendation is simple: If you don’t need it, disable it!

There are 3 settings to manage Unread Marks for a Notes database:

  1. Don’t maintain unread marks (Database Property – Last Tab)
  2. Do not mark modified documents as unread (Database Property – Tab 4)
  3.  Manage Unread Marks on a Notes View level (View Property – Tab 5)

It’s important to note that if you want to leave Unread Marks enabled for your Notes database and instead specify in your Notes View that there should be no unread marks, the View is still affected. See below abstract from the Domino Designer Help:

Note: Designing views that don’t display unread marks doesn’t improve database performance because they are still maintained but not displayed.

This means that to improve database performance, you have to implement one of the first 2 options mentioned above, at the very least option 2.


I can’t stress enough the impact unread marks can have on a Notes database. If you don’t need it…disable it. Depending on the size of your Notes database, the results are almost immediate.

Cheers for now
14 Mar 2013

Video Tutorial: Get up and running with Lotus Domino Designer 8.5.3

Hi everyone. So here’s my next Video Tutorial. I show you how to download Lotus Domino Designer 8.5.3 and I also give a quick demo on how to set up your first Notes Application.

I decided to go back to basics and assist those who are new to IBM (Lotus) Notes, especially those who want to get started on Notes/Domino and XPages Development. I end off the Video Tutorial showing you how easy it is to create a working CRUD Application (Create/Read/Update/Delete) in the Notes Client.

If you use iTunes, you can download this video via David Leedy’s NotesIn9 Podcast series.

Enjoy :)


21 Nov 2012

Check the Eclipse version of your Lotus Notes 8 Client

Hi everyone. Just thought I’d blog this quickly. I wanted to check which version of Eclipse is being used for my Notes 8.5.3 FP1 Client and it was a touch tricker than expected. Thanks to Nathan T Freeman, I now know where to find this:

1. Open your Notes Client and click on “HelpAbout”.

2. Click on the “Plug-in Details” button.


















3. Sort the “Plug-in Name” Column and search for “Eclipse UI”. You will see the version in the Version Column. In my case it’s version 3.4.2……



This is baseline for determining the overall version of Eclipse that’s used for Lotus Notes.


Hope this helps.


24 Oct 2011

Avoid Annoying Errors in Lotus Notes Mail and Calendar

   For almost a year now, I’ve been using the 8.5 Notes Mail Template, which i thoroughly enjoy. Having said that, something went wrong from upgrading it from the 7 template to 8.5.


Every time I open my mail, i would get a “Type Mismatch on External Name: GETQUOTA”. This same error would occur when I try to delete Calendar Entries (Type Mismatch on External Name: CSEVENTNOTES). While this was frustrating, it was never considered a showstopper, so I learned to live with it.

Having said that, it’s been almost a year, and enough is enough. So, to resolve the issue, i tried the following:

1. Manual Design Replace of the Mail Template (didn’t work)
2. Upgrade Folder Design (didn’t work – According to online searches this is what sometimes caused the error to occur)
3. I deleted every design element in my Mail Database, and then did a design replace. (didn’t work. This is when I started considering database corruption).
4. Copy Style compact of Mail Database (No surprises….didn’t work)

5. Deleted Bookmarks.nsf and Desktop.dsk (didn’t work, and now I had to setup my workspace again)
Sadly, I was getting poor results from Google. THEN, a thought occurred to me. Whenever I develop and deploy applications to my clients, I always make a point of performing 2 operations:
1. Signing the Application I’m deploying.
2. Re-compiling the application design to ensure that all LSS Files and Code Dependencies are rendered properly.
In my head, Step 2 (Re-Compiling the Design) seemed like a worthy try. Low and behold, IT WORKED first time!!!

So, my fellow coders, when you are faced with Errors that just seem out of your control, which suggest possible corruption, always try a Re-Compile before throwing in the Towel.For those who are curious how a Re-Compile works, do the following:

1. Open your Application in the Domino Designer.
2. In the Top Menu, click on ToolsRecompile All LotusScript
This will take about 30 seconds to run. What this does is: loop through every design element in the database, and wherever there is LotusScript referenced, it re-compiles the code to ensure that there are no errors in the code, and that nesting elements are referenced correctly. This is a very powerful tool, and I recommend using it as a standard when deploying new Applications or updates to existing applications.
I hope this helps you in future.