Date field always displays "None"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created a date needed field and made the type Date/Time. The field always
displays "none". I have tried going to the advanced properties and deleted
"None" as the Value and Text. But it always comes back.
 
This is normal behavior. "None" means no date/time has been selected for that property. Outlook actually stores the date #1/1/4501#.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
My date fields are also displaying 'none', but i want to require that a date
be entered into the field. What validation formula can i enter to make this
happen? Currently I have the [Revision Date] <>"", but this is not working.
 
I use a validation formula like this for date fields:

[Due Date] <#1/1/4501#

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


Aggie G said:
My date fields are also displaying 'none', but i want to require that a date
be entered into the field. What validation formula can i enter to make this
happen? Currently I have the [Revision Date] <>"", but this is not working.

Sue Mosher said:
This is normal behavior. "None" means no date/time has been selected for that property. Outlook actually stores the date #1/1/4501#.
 
Sue Mosher said:
This is normal behavior. "None" means no date/time has been selected for that property. Outlook actually stores the date #1/1/4501#.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
My client doesn't want the field to display 'none' the first time the form is
entered. They insist that the field is blank on a new form. Can you help me
out?

BTW, I have both your books and am currently using Outlook 2003.
 
I am in a similar situation. I have a date field that displays properly in
Outlook 2003 but it displays as "None" in Outlook 2007.

Any help would be greatly appreciated.
 
Sue's not available.

What date field is this, a user property or a built-in property?

If a user property is this in a custom form or standard form? If a custom
form where is the form published?

If you view it in Outlook 2003 it shows a date but in Outlook 2007 the very
same item's property shows None?

Exchange mailbox or PST file?
 
Helo Ken,

Thank you for your prompt reply.

To answer your questions: The date/time field is called Due By and it is a
user property. The form is a custom form and we are using exchange mailboxes.

The form is a work order request application and there is a compose page and
a read page. The field displays with an initial value of "None". The user
is required to enter in a date prior to sending the form.

After further testing, we've discovered that the date does not display if
the form is sent from Outlook 2007 and you send the form to yourself. We
have employees that like to CC themselves for their own record.
 
If the form is sent to themselves is it the custom form MessageClass?

If you check in the items sent from Outlook 2007 do they have that
UserProperty there at all?

Is the custom form published anywhere?
 
The form is MessageClass IPM.Note

In the sent items, the date does not display properly.

Unfortunately, the form is not available publicly.
 
In general a user property will not be preserved when an item is sent out
and then received. If your users are sending to themselves also then the
received item probably won't have that property unless it's received as a
custom form with that property there. But even that may not work.

That's different than what you said in the last post that users Cc
themselves and the received copy doesn't have the property.
 
Ken,

My apologies if I'm not explaining things properly. I did not create the
form and my knowledge of Outlook forms is limited.

The property works perfectly if the form is sent using Outlook 2003 so this
appears to be a limitation of Outlook 2007.
 
I'm not aware of such a problem or limitation, but I'd have to see the
actual form to go any deeper into any troubleshooting.
 
I could probably look at it, but I can't guarantee when I'll have the time
to do so.
 
Back
Top