Hi,One of the biggest issues I encounter while developing Domino applications is to clean up and remove obsolete fields from the UNK table. To do so, I need to know which documents, which forms, etc, reference an obsolete field so I can remove those references. Is there a way to make Domino systematically list the documents and forms that reference a certain field?
Subject: Systematically finding where a field is referenced
There is a tool to list fields (from the UNK table) and where the fields are used. The tool, itemdef.exe, can be downloaded from IBM at http://www-1.ibm.com/support/search.wss?q=itemdef.exe . I run it with the -F option and pipe the output to a temporary file.
The sorted output shows the fields in increasing order of usage. Fields that are in only a fiew notes show the note IDs where those fields are used. In addition, the bottom of the output lists fields not found in any document.
To remove unused fields from the UNK table:
-
Delete the database’s Full-Text index (if any).
-
Then compact the database.
- Gene
Subject: *Does the R5 version work with ND6/6.5, do you know?
Subject: *Does the R5 version work w/ND6 …Yes
I am using it with ND6.5.1 . I have added a custom tool to my designer client. The formula I use is:@Command( [Execute];“C:\Lotus\extras\itemdef.bat”; @Name([CN];@DbName[1]) + “!!” + @DbName[2] );
The itemdef.bat file refered to above is a batch file that executes the itemdef.exe with the -F option and with the database server and database name passed as a parameter. The output is redirected to a temp file. Then notepad is launched to view the output. The itemdef.bat file looks like this:
c:\lotus\extras\itemdef.exe -F %1 > %TEMP%\itemdef.tmp
start notepad.exe %TEMP%\itemdef.tmp
- Gene
Subject: Systematically finding where a field is referenced
The UNK table lists item names, rather than field names. That is, it includes items that are created by code and that do not match fields in any form. Items might be used by code and design elements that you do not have access to – for example, by private views, by agents in other databases, or by local code in Notes client machines. So it is impossible to make a complete list of where an item is used, and impossible to be completely certain that an item is obsolete.