![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
Giving the user a choice in the date field...
I'm building a membership directory database. I want birth dates and
anniversary dates, but, being the fickle folks some are, I want those who are proud of their age to be able to enter month, day, and year, and those who are a bit more private to be able to enter month and day only, leaving the year blank. Yes, this could be a free form text field, but I'd rather it be a time/date field so I can run reports that will let me know who gets birthday/anniversay notices in our church newsletter. Thanks! |
|
|||
|
Re: Giving the user a choice in the date field...
a date/time field will store a complete date, no exceptions. if you don't
enter a year, i believe the date will default to current year. for data entry / display purposes, you can format the form/report control to show only the month and day. with a bit more work, using VBA code, you should be able to display complete dates for those members with "real" dates, and month/day for the others - if your members are all adults, some reasonable time frame cutoff should work, at least for the next 17 years or so. hth "rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in message news:82497E54-156B-409C-9AEB-BF0B8311F86B@microsoft.com... > I'm building a membership directory database. I want birth dates and > anniversary dates, but, being the fickle folks some are, I want those who are > proud of their age to be able to enter month, day, and year, and those who > are a bit more private to be able to enter month and day only, leaving the > year blank. Yes, this could be a free form text field, but I'd rather it be > a time/date field so I can run reports that will let me know who gets > birthday/anniversay notices in our church newsletter. > > Thanks! |
|
|||
|
Re: Giving the user a choice in the date field...
You don't need a date time field for your reports. Look at the DateSerial
function in the Help file. Use three separate fields for Year, Month and Day and make them number data type. Steve "rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in message news:82497E54-156B-409C-9AEB-BF0B8311F86B@microsoft.com... > I'm building a membership directory database. I want birth dates and > anniversary dates, but, being the fickle folks some are, I want those who > are > proud of their age to be able to enter month, day, and year, and those who > are a bit more private to be able to enter month and day only, leaving the > year blank. Yes, this could be a free form text field, but I'd rather it > be > a time/date field so I can run reports that will let me know who gets > birthday/anniversay notices in our church newsletter. > > Thanks! |
|
|||
|
RE: Giving the user a choice in the date field...
Thanks. This makes perfect sense.
Michael "rhodesmk@swbell.net" wrote: > I'm building a membership directory database. I want birth dates and > anniversary dates, but, being the fickle folks some are, I want those who are > proud of their age to be able to enter month, day, and year, and those who > are a bit more private to be able to enter month and day only, leaving the > year blank. Yes, this could be a free form text field, but I'd rather it be > a time/date field so I can run reports that will let me know who gets > birthday/anniversay notices in our church newsletter. > > Thanks! |
|
|||
|
Re: Giving the user a choice in the date field...
Thanks. This makes perfect sense.
Michael "tina" wrote: > a date/time field will store a complete date, no exceptions. if you don't > enter a year, i believe the date will default to current year. for data > entry / display purposes, you can format the form/report control to show > only the month and day. with a bit more work, using VBA code, you should be > able to display complete dates for those members with "real" dates, and > month/day for the others - if your members are all adults, some reasonable > time frame cutoff should work, at least for the next 17 years or so. > > hth > > > "rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in > message news:82497E54-156B-409C-9AEB-BF0B8311F86B@microsoft.com... > > I'm building a membership directory database. I want birth dates and > > anniversary dates, but, being the fickle folks some are, I want those who > are > > proud of their age to be able to enter month, day, and year, and those who > > are a bit more private to be able to enter month and day only, leaving the > > year blank. Yes, this could be a free form text field, but I'd rather it > be > > a time/date field so I can run reports that will let me know who gets > > birthday/anniversay notices in our church newsletter. > > > > Thanks! > > > |
|
|||
|
Re: Giving the user a choice in the date field...
Worth checking in to. Thanks for the info.
Michael "Steve" wrote: > You don't need a date time field for your reports. Look at the DateSerial > function in the Help file. Use three separate fields for Year, Month and Day > and make them number data type. > > Steve > > > "rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in > message news:82497E54-156B-409C-9AEB-BF0B8311F86B@microsoft.com... > > I'm building a membership directory database. I want birth dates and > > anniversary dates, but, being the fickle folks some are, I want those who > > are > > proud of their age to be able to enter month, day, and year, and those who > > are a bit more private to be able to enter month and day only, leaving the > > year blank. Yes, this could be a free form text field, but I'd rather it > > be > > a time/date field so I can run reports that will let me know who gets > > birthday/anniversay notices in our church newsletter. > > > > Thanks! > > > |
|
|||
|
Re: Giving the user a choice in the date field...
you're welcome :)
"rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in message news:55A51A61-6707-48E4-A664-108859F5A30D@microsoft.com... > Thanks. This makes perfect sense. > > Michael > > "tina" wrote: > > > a date/time field will store a complete date, no exceptions. if you don't > > enter a year, i believe the date will default to current year. for data > > entry / display purposes, you can format the form/report control to show > > only the month and day. with a bit more work, using VBA code, you should be > > able to display complete dates for those members with "real" dates, and > > month/day for the others - if your members are all adults, some reasonable > > time frame cutoff should work, at least for the next 17 years or so. > > > > hth > > > > > > "rhodesmk@swbell.net" <rhodesmkswbellnet@discussions.microsoft.com> wrote in > > message news:82497E54-156B-409C-9AEB-BF0B8311F86B@microsoft.com... > > > I'm building a membership directory database. I want birth dates and > > > anniversary dates, but, being the fickle folks some are, I want those who > > are > > > proud of their age to be able to enter month, day, and year, and those who > > > are a bit more private to be able to enter month and day only, leaving the > > > year blank. Yes, this could be a free form text field, but I'd rather it > > be > > > a time/date field so I can run reports that will let me know who gets > > > birthday/anniversay notices in our church newsletter. > > > > > > Thanks! > > > > > > |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|