Backtrack every Month Structure
Setting the structure of a Template to Backtrack Every Month, allows you to forget about the fact that not all months have the same number of days and that they do not all start on the same weekday.
A month can extend over a maximum of 6 partial weeks. This is the case for 30-day months that begin on a Sunday, or 31-day months that begin on a Saturday or a Sunday.
Q++ uses this to set aside DayValues for each month-block of a Backtrack EveryMonth grid. DayValues from 1-42 (six weeks time 7 days) belong to the first month-block, DayValues from 43-84 belong to the second month-block etc…
Each month-block behaves as a dairy grid containing a single month :
|•||You can choose to hide the outside days.|
|•||You can even have 5-week month-blocks by having DayValues ranging from 1-37, where the DayValues 36 and 37 are piggy-backed onto DayValues 29 and 30. The fact that DayValues 38-42 do not exist will be ignored by Q++.|
The date corresponding to the first DayValue of a month-block will depend on the setting used for First Date of Template.
One important consequence of the use of 42-days month-blocks is that a token with DayValue=42 can actually represent a later date than a token with DayValue=43, sometimes by as much as 13 days !
The Backtrack Every Month setting does not limit you to neatly ordered grids where each month-block is on one page. The next topic shows an example where each month straddles both pages of the grid.