There *aren't* any fields requiring only the year. Sometimes the users know
only the year when they're inputting data so they'd like to put it there but
it's a date field so won't accept only the year. Hence Sparks' question.
With your scenario there's 2 solutions:
1 - The date text box can be bound to the table but when only the year is
known, it can't be input into the same text box, meaning another text box on
the form. That additional text box would be unbound and need code to make it
work right.
2 - Use one unbound text box with the code to work with the input value
whether it's a full date or a year. Having unbound text boxes on a bound
form can produce problems when trying to save to record, especially if the
unbound text box is meant to transfer input to a required column.
Either way that's more code, more complexity, and more chances for errors and
frustration for the user.
Keep it simple. A bound date field.
Chris
Microsoft MVP
paii, Ron wrote:
>I agree with you to not break a date into 3 number fields. But why force the
users to enter a default day and month on the fields requiring only year?
The form can easily accept year input, append the default day and month,
then store it in a date field.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200809/1 
