10/14/2016 10:23 AM | |
Joined: 12/18/2014 Last visit: 8/14/2024 Posts: 33557 Rating:
|
As already mentioned, the month February is the real problem due to a possible leap year. I hope I have not overlooked anything. AttachmentThursday.zip (162 Downloads) |
This contribution was helpful to
1 thankful Users |
10/17/2016 7:04 AM | |
Joined: 1/16/2013 Last visit: 6/7/2022 Posts: 47 Rating:
|
Hi, thank you for your solution. It is clever and “automatically” works until 2032 but needs TOO MUCH blocks. It is problem. I think the best solution (with minimum blocks) will be looking for first Thursday in new month and problematic months add separately. In the year 2017 it is September and December. In the beginning of ach year (2018,…) I will have to add new problematic months. Solution in attachment. Carlos AttachmentThursday_2.zip (152 Downloads) |
10/17/2016 8:39 PM | |
Posts: 124 Rating:
|
Hello Ixo, Like you well posted, a problem occurs when Friday is the first day in any month. These are our "Friday first". But there is a solution. We can use a yearly timer setting <montly> and <days> 1 to 7. Also, we need add "Exceptions": yearly timers for all "Friday first" (2017 will have 2, 2018 will have 1, 2019 will have 3…). The good new is: when Friday is the first day in any month, the next Friday will be 8. Then, Thursday will be 7. So, the yearly timer setting <montly> and <days> 1 to 7 goes to "0" state at this day. That means there is no duplicity in a month with "Friday first". I think to be right. I did not see your solution. It can be better than this one. Regards, AttachmentFirst Thrusday for all months V2 17 10 2016.zip (151 Downloads) |
Last edited by: Dinos at: 11/13/2016 7:07:38 AM |
|
Follow us on