Hi Leo,
I'm not sure you necessarily want to store such a calculated field, since storing the results of
any calculation violated 3rd normal form (3NF) for database design. However, it is certainly
easy enough to add 30 days to a date value and display it in a query or a textbox on a form or
report. Use the DateAdd function to accomplish this:
The syntax is: DateAdd(interval, number, date)
where interval is a string (use "d" for days), number is the number of intervals, and date is the
field that stores your starting date.
In query design view, you can add a new field, as follows:
Field: Due Date: DateAdd("d",30,[StartDate])
where StartDate is the name of the field where you enter the beginning date. There are also
functions available to calculate 30 working days, where you do not include weekends or company
holidays, however, you cannot use the DateAdd function to do this. If you need to exclude
weekends & holidays, then check out the functions available at:
http://www.mvps.org/access/datetime/date0012.htm.
Tom
_________________________________________
Does anyone if you can put in a date in one field, and
than have access count a certain number of days and
populate another date field automatically? For example,
if I put in January 1 2004 and my due date is always 30
after, Access would automatically enter January 31 2004
into the DUE DATE field, or something like that?
