Prev: Slow running reports
Next: data checking
From: Jeff Boyce on 27 Apr 2010 14:51 Unfortunately (and it may be just me), when I have to go back later (even a few months later) and figure out what I was doing (and thinking?!?) in an application, I AM worried. I try to leave breadcrumbs and simplify as much as possible ... because I MAY be the only one that has to use the db! <g> If you add a date/time field to your table and call it something like [DateOfBirth] (or, if you have a really really good memory, [DOB]), you would enter the individual's birthday. Then, in a query, you could call a function (a procedure you write that returns a value) to derive the age category your original post mentioned. To determine something like "age", there are a lot of examples of code you can find by searching on-line for "calculating age from birthdate" and "MS Access". Good luck! Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. ".:RoKsTaR:." <RoKsTaR(a)discussions.microsoft.com> wrote in message news:033B1C1C-E78E-499F-A177-C70DCA21F59B(a)microsoft.com... > That's a really cool idea, great thinking! How's that done? > > I'll be the only one using this database, so I'm not to worried. However, > anything to make it work better is great :)
From: .:RoKsTaR:. on 27 Apr 2010 15:30
great, I'll look into that :) |