Forms - unknown field requires a value

Status
Not open for further replies.
S

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?
 
S

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?

Sue Mosher

"Scholastica" <Scholastica> wrote in message

news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> 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?
 
S

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]" wrote:


> 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?

> > Sue Mosher
> > >

> "Scholastica" <Scholastica> wrote in message
> news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> >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?


>
 
S

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

"Scholastica" <Scholastica> wrote in message

news:43237DC4-E6E4-4764-9DB4-9CA27304ECBC@microsoft.com...
> 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]" wrote:
>
> > 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" <Scholastica> wrote in message
> > news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> > >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?

>

>
>>
 
S

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.

"Sue Mosher [MVP]" wrote:


> 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
> > >

> "Scholastica" <Scholastica> wrote in message
> news:43237DC4-E6E4-4764-9DB4-9CA27304ECBC@microsoft.com...
> > 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]" wrote:
> >
> >> 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" <Scholastica> wrote in message
> >> news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> >> >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?
> >
> >
> >>


>
 
S

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]" wrote:


> 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
> > >

> "Scholastica" <Scholastica> wrote in message
> news:43237DC4-E6E4-4764-9DB4-9CA27304ECBC@microsoft.com...
> > 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]" wrote:
> >
> >> 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" <Scholastica> wrote in message
> >> news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> >> >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?
> >
> >
> >>


>
 
S

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

"Scholastica" <Scholastica> wrote in message

news:23EAD477-6799-4545-B8C9-950798C5A284@microsoft.com...
> 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.

> "Sue Mosher [MVP]" wrote:
>
> > 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.



>

>
>> "Scholastica" <Scholastica> wrote in message
> > news:43237DC4-E6E4-4764-9DB4-9CA27304ECBC@microsoft.com...
> > > 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]" wrote:
> >> >> 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" <Scholastica> wrote in message
> > >> news:27B23050-17D9-4B53-AFBC-A9648467E218@microsoft.com...
> > >> >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?
> > >
>> >
>> >>

>

>
>>
 
Status
Not open for further replies.
Similar threads
Thread starter Title Forum Replies Date
V Is it possible to collect statistics from Outlook forms? Outlook VBA and Custom Forms 1
V Modifying the built in forms with VBA Outlook VBA and Custom Forms 4
V Outlook Forms: Formatting a Label with 2 different styles Outlook VBA and Custom Forms 1
F KB4475563 stops VBS at forms working Outlook VBA and Custom Forms 3
N Creating a button or link to a form in the Organizational Forms Library Outlook VBA and Custom Forms 3
N Outlook Forms Help Outlook VBA and Custom Forms 2
M other user's mailbox won't open, forms disappeared Using Outlook 42
J Backup .OST - Custom Contact Forms, Defined Fields, Notes Using Outlook 1
B Outlook Custom forms Using Outlook 0
Diane Poremsky Organizational Forms Library in Exchange 2010 New Slipstick.com Articles 0
Diane Poremsky Create an Organizational Forms Library New Slipstick.com Articles 0
Diane Poremsky Create an Organizational Forms Library in Exchange 2013 or Office 365 New Slipstick.com Articles 0
G Looking for help with our Organization Forms Library Outlook VBA and Custom Forms 1
Cameron Piper Automatically update custom forms across multiple computers Outlook VBA and Custom Forms 1
F Organizational Forms usage Exchange Server Administration 1
K Export Organizational Forms Library Exchange Server Administration 1
N Export Outlook custom forms fields to excel Outlook VBA and Custom Forms 1
Diane Poremsky How to clean up Outlook's Forms Cache New Slipstick.com Articles 0
X Bulk edit Contact forms Using Outlook 2
Diane Poremsky Designing Custom Outlook Forms New Slipstick.com Articles 0
Diane Poremsky Create an Organizational Forms Library in Exchange 2013 New Slipstick.com Articles 1
Diane Poremsky Publishing Custom Forms New Slipstick.com Articles 0
G Message template / custom forms and VBA Help needed - inserting info into table Outlook VBA and Custom Forms 3
N How to disable user defined fields in BCM forms Using Outlook 2
N Passing Attachments between forms? Outlook VBA and Custom Forms 2
Nick Truscott Lost custom forms after moving mailbox Outlook VBA and Custom Forms 3
S How to remove forms from Organizational forms library Outlook VBA and Custom Forms 2
G Outlook forms text input Outlook VBA and Custom Forms 1
H Lost Custom Forms when we replaced Exchange Server Outlook VBA and Custom Forms 3
J Outlook 2013 Forms Issue Using Outlook 1
N Outlook Forms Not Displaying Outlook VBA and Custom Forms 6
D Using Follup in Custom Forms Outlook 2013 Using Outlook 9
P Custom Forms in Reading/Viewing Pane Using Outlook 1
D Move Personal Forms Library Outlook VBA and Custom Forms 10
C Custom Forms: Question about retaining form information throughout the entire conversation Outlook VBA and Custom Forms 2
K Outlook Crash on referencing forms Using Outlook 1
M does outlook 2013/365 on mac support custom forms? Outlook VBA and Custom Forms 1
R Viewing & Using custom forms/tasks in Outlook 2013 Using Outlook 1
LarryH Custom Fields & Forms Using Outlook 3
W Outlook 2010 Forms Using Outlook 1
L Published Forms Using Outlook 0
P Field in Forms displayed depending on the Item chosen from drop-down-list BCM (Business Contact Manager) 1
G Questions on creating Outlook forms Using Outlook 0
P Creating custom contact forms Using Outlook 2
E Changing layout of forms in BCM Using Outlook 1
O Outlook 2013 and Organizational Forms Library Using Outlook 2
M Outlook 2010 Forms Using Outlook 1
O Outlook 2003 forms problem Using Outlook 3
M Add custom locations to Outlook Forms "Look In:" drop-down list Using Outlook 5
J Update Outllook 2010 to Outlook 2013 - Incorrect Forms Using Outlook 2

Similar threads

Top