Entourage 2008 users who rely on week numbers know that only one calendar view shows the actual week number -- it only appears on the 7-day Week calendar. I've written an AppleScript to add week numbers to the first Sunday of every week of the chosen year so that we can see week numbers in the monthly calendar view too, where I find them more useful.
How to Install
- Download the Add Week Numbers 1.0.scpt.zip file and double-click it to extract the Add Week Numbers 1.0.scpt script.
- In Entourage 2008 select About This Menu... from the AppleScript menu
and click the Open Folder button.
This will open your Entourage Script Menu Items folder. The full path to the folder is ~/Documents/Microsoft User Data/Entourage Script Menu Items where " ~ " is your home folder. - Drag the Add Week Numbers.scpt file into the folder.
How to Use
This script adds a new all-day calendar event on every Sunday for the specified year. Each event is set with a "Free" status and is named for the number of the week and the ordinal date for the current year (days numbered 1-365).
- Select Add Week Numbers from the AppleScript menu in Entourage.
- Enter a year where you'd like to add dates.
- The script may take about 10-20 seconds to populate calendar with the week numbers.
Note: Only your default calendar will have the week numbers added to it. To add week numbers to a different calendar, select Accounts... from the Tools menu, select the account for the secondary calendar and click the Make Default button. Run the script and then reset your default calendar in the Accounts... window.
Comments (15)
It tells me 1 januar 2008 is an invalid date. I guess it doesn't like non-US date formats?
You don't need to specify a complete date, only a year. Just enter "2008".
Do you have a script to remove these events?
No, and I won't create one because I don't want to be responsible for deleting someone's content. While I can probably create a script to do this, if something goes wrong I would be blamed whether or not the script is at fault.
You can select File --> New --> Saved Search while viewing your Calendar and create a search to find what the script has added.
Start with Subject Begins With Week and add further criteria to filter out any events not created by the script.
Then Shift click or Command click to select multiple items and tap the Delete key.
I did this, it made the first sunday/week of 2009 week 2.
So everything's now a week out.
Any fix?
Mike
Hi Mike!
The script's doing what it is suppose to do. Week 1 is considered the week where the first day falls, not the first full week.
it doesn't work...
I'm willing to provide some support for my scripts but you'll need to give me more than just "it doesn't work...". What steps are you following and what happens when you try?
great script! thanks
Works fine! - but only displays week number when viewing one week at the time - in the full month view, the week number is not displayed. Is that as it should be? - if so, I would like it to be a little bit different :-)
The script creates all-day "free" events on each Sunday of the selected year. So long as you can see one of these week numbers on a Sunday in one view then you'll be able to see it on the same Sunday in any other view.
Hi! Worked fine for 2009 but I am getting this error for 2010 which I can't fathom?
error "Invalid date and time date January 1, 2010 of «script»." number -30720
Any suggestions??
No idea what's happening. The script does the same thing regardless of year. Check for errant characters such as spaces before or after the date.
The script is your original untouched script which I ran successfully last year to put 2009 in my calendar - it worked fine.
By way of testing, I have just tried to rerun the previously successful run for 2009 and I get the same message as I do for 2010.
Of course this year I am running Snow Leopard and
Entourage 12.2.3 - perhaps something has changed so the script is getting a different return now and failing?
Any pointers please?
The fact you're running Snow Leopard makes a world of difference. Times and dates are now referenced a little differently, but enough to probably break the script.
I'll look into either posting a new script or or an update to the old one.