Re: Counting Days
Hans,
Mark has some good ideas below. I'm responding in a different branch of this thread just to keep our suggestions straight for you.
To accomplish what is mentioned in Example 2, you could create a library table called something like "Weeks" (or whatever your consistent time unit is.) Here's how you might set it up:
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------
Mark has some good ideas below. I'm responding in a different branch of this thread just to keep our suggestions straight for you.
To accomplish what is mentioned in Example 2, you could create a library table called something like "Weeks" (or whatever your consistent time unit is.) Here's how you might set it up:
- Fields: [Week Description], [Week Start Date], and [Week End Date].
- Relate "Weeks" to "Hotel Stays" table one to many (one week can have many hotel stays.)
- Set up an automation to automatically link a [Hotel Check-In Date] [Hotel Check-Out Date] pair on "Hotel Stays" to the parent Weeks table. (See Brian's solution on response 3 for an example)
- Set up report on "Hotel Stays" table to filter based on "Week" for the hotel stay instead of the start and end date.
- i.e. "Show me the # of nights in Week Ending 10/20" instead of "Show me the # of nights between "10/14" and 10/20"
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------