If it was mine--
I'd add a "LastUpdate" Date/Time field and a RevisionNumber Numeric field to the underlying table. Set the RevisionNumber to 1 (or any integer).
You have a form that is used to edit the information in the table (that will appear in the report)? If so, you could use the above new fields as follows:
On the edit form, drag -n- drop the LastUpdate field somewhere so it appears on the form. I'd set its Enabled property to No and Locked to Yes to prevent the user from messing with it, but to let her/him see it. If you don't care about their seeing it, set its Visible property to No and ignore Enabled and Locked.
On the edit form's BeforeUpdate event, write
Me.LastUpdate = Now()
That will automatically update the LastUpdate field whenever the information on the form is edited, just before the new info is stored in the table.
Drag -n- Drop the RevisionNumber field to the form and set its properties the same as for the LastUpdate field.
Put a Save command button on this form. When the user clicks Save, you could code the OnClick event something like
If me.Dirty Then 'Dirty' = 'Data was Changed'
If Msgbox("Data changed. Update Revision no.?", vbYesNo, "Click yes or No") = vbYes Then ' Give user the option of incrementing the revision number by clicking Yes
Me.RevisionNumber = Me.RevisionNumber + 1
End If
End If
This approach avoids the need for the user to make too many decisions and possibly mistype the date or rev. number.
HTH,
Jim
