Calendar Logic

[rokstedy]

I'm in the beginning stages of adding Calendar like features to a database I'm currently managing, but I'm having a heck of a time wrapping my head around the basic structure of such a thing. The basic record will have fields that include entered date, assigned date (to outside contractor), receive date (completed order from contractor), and completed date (to our client).

We have established turn times of a week for each order and I thus would like to setup a calendar that lets me know which orders I should be expecting to be completed on a given day (Entered date + 7).

I'd also like to have the calendar show me how many orders I've received (Entered Date) per day.

These are just two examples, but I guess it doesn't really matter what the examples are. What I can't figure is how this is done!? My first instinct is to create a table with a record for each day, then have that table relate back to the orders and find which orders match for the respective criteria (i.e. date = entered date for orders received each day or date = order due date for those orders expected to be completed today). This seems like the opposite of elegant and I think there are limitatiosn when it comes to setting up the relationships.

Any help!!?

[comment]

See:

http://fmforums.com/forum/topic/42617-basic-monthly-calendar-april-06/

[John Sindelar]

Creating records for each slot isn't necessary. Feel free to take this apart and see how it works, or paste it into your own file: http://www.seedcode.com/cp-app/prod/calendarfree10