[AccessD] Birthday in table

The definition of a leap year is a two-step:

1. if the year is evenly divisible by four then you're cool, except:
2. if the year ends in 00 then it must be evenly divisible by 400 -- thus
1900 was not a leap year but 2000 was.

That should be enough data.

A.


On 6/15/07, Lembit Soobik <lembit.dbamail at t-online.de> wrote:
>
> thanks, Liz,
>
> but I really dont want to know or even estimate if the year isn't given,
> and if the result of the calculation then is 1 year off, I get the same
> problem that 29.02 is not accepted and I have to go back and re- estimate
> and reenter.
>
> seems I have to use 3 textboxes and do my own verification (which isn't
> too
> difficult for the months March thru January, and in case of February just
> ask for confirmation with a messagebox if 29 is entered.
>
> thanks
> Lembit
>
> ----- Original Message -----
> From: <Elizabeth.J.Doering at wellsfargo.com>
> To: <accessd at databaseadvisors.com>
> Sent: Friday, June 15, 2007 4:25 PM
> Subject: Re: [AccessD] Birthday in table
>
>
> >
> > You could try this:
> >
> > Make birthdate field a date, as if you planned to always know the
> > person's actual date of birth.
> >
> >>From your interface, offer the ability to enter any part of the
> > birthdate.  Many of our clients are really after 'approximate age' , so
> > we gave the opportunity to enter '37' in a text box labeled 'Current
> > Age', and then converted that to a birthdate of today's date in the
> > appropriate year.
> >
> > In your case, it would be a little more complex, but if you had separate
> > text boxes for month and day as well as for year, with an approximate
> > age option so you could calculate an approximate year, you could put it
> > all together into a valid date before writing out to your table.
> >
> >
> >
> >
> > HTH,
> >
> >
> > Liz
> >
> >
> > Liz Doering
> > elizabeth.j.doering at wellsfargo.com
> > 612.667.2447
> >
> >
> > This message may contain confidential and/or privileged information. If
> > you are not the addressee or authorized to receive this for the
> > addressee, you must not use, copy, disclose, or take any action based on
> > this message or any information herein. If you have received this
> > message in error, please advise the sender immediately by reply e-mail
> > and delete this message. Thank you for your cooperation.
> >
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Lembit Soobik
> > Sent: Friday, June 15, 2007 9:04 AM
> > To: Access Developers discussion and problem solving
> > Subject: [AccessD] Birthday in table
> >
> > Hi, everybody,
> > I have tried to define a field in an A2003 table - in fact 2 fields -
> > for birthday.
> > thing is, in many cases I know only day and month, not the year.
> > so I tried two fields: DD.MM as first and YYYY as second field.
> >
> > a) it wont let me enter a year, and I had to make it Integer instead.
> >
> > b) I can enter a day and month but it will add the year 2007 (behind the
> > scenes) and therefore wont allow me to enter 29.02
> >
> > now I can of course split it up into 3 fields: DD, MM, YYYY, but this
> > would allow any error resultin in 41.21 as DD.MM
> >
> > so, how do you handle that? or do you allways have the full date
> > including year?
> >
> > thanks for any help
> >
> > Lembit
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.472 / Virus Database: 269.8.16/849 - Release Date:
> 14.06.2007
> > 12:44
> >
> >
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>