Date Table

[Emma]

Hi I've posted this question about 3 times now and still can't find it sorry
for the repeated posting. I have a client table which has an initial date
then the closing date should be 3 months from the initial date. The problem
is the client can enter 3, 6, 9, 12 months ahead. So I need a separate table
to hold an endless amount of renewal dates, each 3 months from the last. Can
someone help me wrap my head around this. I'm trying to use a separate table
for the dates, but I'm not sure how to set it up.. a separate table for each
user or a table that contains all users and their renewal date? Any advice
would be greatly appreciated.

 

[Jeff Boyce]

Emma

You did say "any advice"...

If you already have an initial date, and the client/user can pick 3, 6, 9,
or 12 months, you DON'T need (or want) to store the "followup" date.
Instead, use a query to calculate the date which is (user-selected duration)
months added to (inital date).

Use a query and use the DateAdd() function.

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.

 

[Daryl S]

Emma -

Why do you need to store the renewal dates? You can calculate them any time
from the dates in the table.

When you say the users can enter 3, 6, 9, or 12 months ahead, I assume that
is the date in the table, and that the renewal dates for these records are 3
months past the date entered.

If so, you don't need to store renewal dates anywhere, just calculate them.