Eric:

Me again.... I know once we’ve nailed this one down that others will benefit
from the information….

I’ve discovered a couple of bugs.

Before I explain the bugs, I want to explain EXACTLY what I’ve done. I
believe I’ve followed your instructions precisely. (I started with a blank
standard form just to make sure that other code in my form wasn’t
interfering.)

Inserted DTPicker control on P.2
Bound DTPicker1 control to “Due Date” field
“Property to use:” set to “Value”
"Set the initial value of this field to:" DateAdd("d", 1 , date())
Select "Calculate this formula when I compose a new form"

Code added behind the form
Function Item_Open()
    Item.Getinspector.ModifiedFormPages("P.2").Controls("DTPicker1").Value =
Item.DueDate
End Function

If I run the form from the design window WITHOUT PUBLISHING IT FIRST, all is
well. In other words, if I save the item, reopen it, close it (without any
changes to the item), it closes without prompting me to save it.

However, once I publish the form, if I create a new item using the newly
published form, save it, open it, close it (without any change to the item),
it prompts me to save it.

I tried this two or three times and continue to get the same result ONLY
AFTER PUBLISHING it. I mention this because you mentioned that you couldn’t
replicate the issue. I’m curious as to whether you actually published the
form or whether you just ran it from the design window.

OK. So, to solve this challenge, we added the suggested code:

Function Item_Close()
    If Item.Saved = False Then
                    Item.Save
    End If
End Function

While the code solved the challenge of being prompted to save an item that
hadn’t been modified, it has introduced two new challenges:

1) If you DO modify a record and press ESC or click the “X” close button, it
automatically closes AND saves the item. Usually, when you use ESC or click
the close button, Outlook prompts you to save the item. We need to determine
a workaround for this issue as we don’t want to have all other Outlook items
function one way and this one does something different.

2) I didn’t mention this earlier as it wasn’t an issue until we added the
Item_Close function… I think there is a challenge with the Item_Close
function when a validation rule on a control is set so that the control must
contain a value. I’m not 100% certain that it happens ONLY when there are
mandatory controls on a form, (i.e. it may just be a coincidence and the
underlying issue may be something else altogether) but the challenge
replicates itself 100% of the time when there are mandatory controls on a
form.

To replicate the challenge on your PC, add the Mileage control to P.2 and
set the validation rule so that the control requires data. Publish the form.
Open the form and hit the ESC key. The Script Error “Unable to save this
item. Line No:7” appears. The error appears every time you try to close the
form without completing the mandatory controls. It seems that the error
message is innocuous but I don’t want our users to be bothered by it. I want
them to see the custom messages I’ve created stating which control requires a
value. I don’t know a lot about VB Script, but if we put the validation rules
in VB Script versus in the property control properties, could that suppress
this error? If so, could you possibly let me know the code for making the
Mileage control mandatory (and a corresponding error message) and I can adapt
it to my form?

Again, I apologize for the length of this post, but I believe all the
details are necessary.

Dave