Browse Prior Art Database

UNK Cleaner - Lotus Notes Design Garbage Collector & Remover.

IP.com Disclosure Number: IPCOM000014442D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 9 page(s) / 102K

Publishing Venue

IBM

Abstract

UNK Cleaner Lotus Notes Design Garbage Collector Remover. Title:

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 17% of the total text.

Page 1 of 9

UNK Cleaner - Lotus Notes Design Garbage Collector & Remover.

___________________________________________________________________________

Title:

UNK Cleaner - Lotus Notes Design Garbage Collector & Remover.

Brief description:

The invention is a tool which releases space in Lotus Notes databases by removing unused design elements not normally accessible to developers. This results not only in increased performance but it also extends the life of these notes Databases by allowing developers to further enhance the application by adding more design elements as needed.

Background technical information needed to understand the utility of this tool:

What does a Lotus Notes/*Domino database consists of:

A Lotus Notes database consists of design and data elements. The interest of this tool is in the design elements. The most common design elements of a Lotus Notes database consists of - database, script libraries, forms, views, folders, fields on a form, columns of a view, etc. Each of these elements is in turn made up of smaller elements like - fields (for forms), columns (for views), event scripts (for script libraries, or database functions).

Where and how does Lotus Notes/Domino store design elements?

All these design elements of a Lotus Notes database are stored as 'fields' in a table called the UNK Table. This table is a part of the Notes database itself.

E.g.,

1. Creating a blank database without any form or view or any other elements, creates 12 fields in the UNK table, which among other data will store the design version, the title, the icon bitmap, signature, and other design elements. (Figure 1)

2. Creating one blank form adds 4 more fields to the UNK table.

3. Creating one blank view adds 3 more fields to the UNK table

4. Adding one field in one form adds 1 field to the UNK table. Now here is the interesting part. As soon as you add any script to any of the field events like 'entering event' or 'exiting event'; it creates 2 additional fields for this one field. The field naming convention is - $fieldname_O (stores the compiled form of LotusScript) and $$fieldname (stores the actual source code)

1

Page 2 of 9

What are the limitations to this type of architecture?

The UNK table (design repository) has a limit of 64k. This limit still exists in all releases of 4.x up to and including 4.6x. If the UNK limit is being reached, you get a specific error message saying, "Database has too many unique field names". The UNK Table is derived from a list of the unique field names in a database. This list contains the field names, data type and other related information. Because the length of field names vary, it is not possible to pin down an exact number of fields that a database can contain before maxing out the UNK limit. On average, most databases can store around 3,000 field names before hitting the limit. Due to the way the UNK table is built, if your database has fewer field names, or shorter field names, the UNK table will be smaller...