Forms - unknown field requires a value

[Scholastica]

I created a great form for my contacts using Outlook 2002. It was working
grand. I upgraded to 2007. It was still grand. Then I thought to add a new
field. I was having a frustrating time figuring out how to set up the fields
(user field based on checkbox - don't go there) so I deleted the new fields
I'd created. I ran the form. The form insists that a field requires a value
and it will not save anything until then.

1. I entered data into all fields. Ran the form and got the same result
(field requires value...)
2. I edited the form and 'selected all' to ensure I didn't have any hidden
fields that I might have missed. None.
3. I deleted a group of fields, ran the form to see if I had deleted the
"culprit" (I had not). I restored the deleted fields, deleted another group,
tested the form restored those, etc. - no change - still told a field
requires a value.
3. I deleted my custom field from "All Fields". No change. HOWEVER, the same
field is still listed in field chooser. Field chooser does not allow me to
delete the field from it's list.
5. I tried saving the form with a new name. No change.
6. For reasons unknown to mankind, I published the form. Now I cannot update
my old contacts because when I try to save the data I'm prompted that 'a
field requires a value'.

Any thoughts on how I can resolve this without having to create a new form
from scratch?

 

[Sue Mosher [MVP]]

Sounds like you've been deleting controls on the design surface, not
deleting the fields that may have been added earlier and set up with
required values. Under #3, did you check both User-defined Fields lists --
In This Item and In Folder?

 

[Scholastica]

This all happened prior to my starting #3. When I was deleting things I was
doing a basic delete - selected an area of fields and hit delete. Ran the
form to see if by deleting any of those, it might narrow down my search. Then
I used "undo" to bring those back, selected another group of fields, etc.

When I first created the fields, I choose a check box. I saw that it needed
a "value" from another source. I created a "userfield1". Renamed it by title
and display. AND made it hidden. Went back into the checkbox settings and
selected that field under value. Ran the form. It worked. I then wanted to
add an additional field. I started that. I published that form. Outlook
automatically updated all my contacts!!!! HOW??? This is when the "a field
requires...." showed up. Before going through the above (deleting, etc.) I
did change the properties in that one field to visible.

I think this is a quirk in 2007. Design surface? Would that be the
"background". If I don't know what a setting means, I leave it alone. I've
created forms before. This is a first. I need to take a look at your book! I
haven't seen one regarding this topic and I looked everywhere (several years
ago tho!)

 

[Sue Mosher [MVP]]

This is no quirk but a basic form design principle -- the controls that
display data in the UI and the fields that store data in an item are two
different things. What you're describing is the deletion of controls, not
fields. Removing a control from a page (the design surface) does not delete
any field associated with that control. The fields are still present in the
form design, and any validation associated with the field also is still
present. You can see the validation settings for a field only through the
Properties dialog of a control bound to that field. In other words, if you
want to see the validation for a field that no longer has a control on a
form page, you'll have to add one: Drag the field from the Field Chooser to
a blank page.

Delete the actual fields through the All Fields page, but notice that there
are two lists of User-Defined fields, and any field you want to delete needs
to be removed from both.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54

 

[Scholastica]

I've already deleted the field from both of those lists. I figured they'd
still be "there" so to speak. I've deleted ALL user-defined fields - in both
lists. I went back and used field chooser to verify (for myself) that the
fields wouldn't show up. They did not. I ran the form and get the same
message.

 

[Scholastica]

Sue - I'm so glad I came across you on this forum. I have a gift certificate
from Amazon and am investing it into your book! I read a couple brief pages
from it and can tell this is what I've been looking for. I'm just doing this
for fun - but one time I actually created a custom form for a Chairman I once
supported as a temporary EA. How cool is that!

 

[Sue Mosher [MVP]]

Standard fields can also have validation added to them. You may need to
check the built-in fields to see if they've been set to require a value.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54