track field names that were changed

I get a " no formula specified for computed field" error.  Am I missing something?

I'm not sure.  My solution does not require any fields on the form.  Which field is generating the error?

The Modifications field; I'm not sure I'm I'm clearly explaining what I want.

I want this subform to track edit history, specifically the following :

person that made the change, date the change was made, labels of the fields that were modified


I want the subform to look like this when it's viewed in the main from.

for example :

Editor:                       Date of Change:             Fields Changed
Pete Johnson            3/13/95 13:25                Description; system contact
Nicky Johnson            6/15/99 15:36                Key contacts
Jon Johnson              8/12/06 17:40                 Interests; Description
Magic Johnson           2/22/07 19:12                Hobbies, Spouse

Bill is proposing some code for you to modify.  The basic idea works, but rather than record anything specific, he just shows what fields you have changed with:

   Msgbox "Field changed:" & fieldName

You could instead replace that line with:
If changedValues = "" then
   changedValues = fieldName
Else
   changedValues = changedValues & "; " & fieldName
End If

That gets the list into a variable, similar to the "fields changed" column that you showed.  The next step is to add some code at the end of the Forall/End Forall loop to actually store this to the Modifications field:

...
End Forall
If changedValues <> "" then
   changedValus = userName & Chr$(9) & Now & Chr$(9) & changedValues
   if doc.Modifications(0) = "" Then
      doc.replaceItemValue "Modifications" , changedValues
   Else
      doc.getFirstItem("Modifications").appendToTextList changedValues
   end if
   changedValues = "" 'reset in case user saves again in this session
End If

This will still leave you with the error you mentioned.  That's because your computed field is expecting you to put in some formula language to actually compute it.  Instead, we are letting the form's LotusScript compute it -- so the field's own calculation shoudl be "whatever is in me, leave it alone" -- in other words, the fields formula should be just its own name, MODIFICATIONS

Still another problem: That tracks all changes to the form, including things that were changed not under the user's control, like the system field ($UpdatedBy, etc.), and your own computed fields.  Modifications field itself could present a problem.  More likely you want to have a list of specific field to either exclude or include. I'll leave that to you to decide upon and figure out.

Thank you qwaletee.  He is right.  My code was just an example of how to determine when a field has changed value.  It's up to you to decide how to store that information.  I recommend saving it to a releted record (a response document, for example).

Ok.  thanks for the help.  I'll try this out and let you guys know.