This workaround is not ideal--workarounds seldom are--but it seemed the simplest solution given the wrapping restrictions caused by the parallel list field approach. Another alternative might be to hide all the core list fields and concatenate their values into one list display field. This approach wouldn't easily support a columnar display, however.

The Web interface is slightly different than the Notes interface, since it can't use LotusScript interactively. It simply displays the fEHDescription field for direct editing and doesn't provide a popup or enforce that a description actually be entered. One useful enhancement for the tool might be to run JavaScript on form submission that better imitates the Notes interface.

Demo
Normally, you'll want to add the special settings fields to your form as hidden display fields. But to demonstrate these features effectively through the user interface, the second example form (frmEHSampleCall2, pictured in Figure C) makes these fields visible and editable.

FIGURE C


Here's the Editor History demo form on the Web client. Roll over picture for a larger image.

To see the effects of each setting, try creating several sample documents and saving them multiple times from both clients under various settings.

Installation
Now that we have looked at the Editor History tool's various features and settings, here's a list of steps to follow when installing the tool into your own application.

First, insert the sfrmEH subform into a host form. You may wish to add a title and collapsible section to the form around it.

Optionally, you can add special hidden fields to the host form to override the subform's default settings as follows:

• Create a hidden numeric display field named fEHMax and give it a value >= 2, representing the window of recent revisions which you wish to track. Beware of very large numbers or the history may exceed the Notes 64K limit for field sizes (default value = 5).

• Create a hidden numeric display field named fEHInterval and give it a value >= 0, representing an interval in seconds. If the last edit was made within that interval, consecutive saves by the same editor won't be appended; they will simply replace the last edit record (default value = 0).

• Create a hidden text display field named fEHPrompt and give it a value of "1" (default value = "").

• Create a hidden text display field named fEHDesc containing any additional information you wish to display in the subform's footnote (default value = "").

Downloads
The Editor History tool is completely contained in the sfrmEH subform included in the sample database I made available at http://www.bigfoot.com/~jonathancoombs. The database also includes the samples described in this article.

Jonathan Coombs is a software developer for Joseph Graves Associates, Inc., (at http://www.jgraves.com) located in Indianapolis. JGA is a full service consulting firm that delivers quality IT services and customized E-commerce, Internet, and Document Management software solutions. Jonathan's professional interests include software reuse, Lotus Notes and Domino technology, and computational linguistics. He can be reached at jonathancoombs@bigfoot.com or (317) 814-8000.