Thanks to the Tracks contributors for a great product.

I use Outlook at work and wanted a convenient way of turning mail messages into Tracks todo items. After a minor struggle with VBA, a workable solution exists.

This macro adds a new item to the right-click context menu which allows Tracks todos to be created directly from the Outlook application. It can currently set the Todo context and project, but does not deal with tags, ‘due by’ and ‘show from’.

I don’t think end-user developed Outlook macros were meant to be shipped around, but installation is not too painful in the end. The procedure is documented in the wiki, at:

http://www.rousette.org.uk/projects/wiki/Outlook-Integration/

All feedback appreciated.

Greg

Installation went well, but Outlook 2007 nags me at every start. Anyway to sign the code?

I’m not sure why, but the form never shows. When I select Add to tracks, it just shows an empty email…

Hi Reinier

Thanks for your feedback.

I have not tested Outlook 2007 - I will install and attempt to isolate the issue.

I am not sure if Outlook VBA macros can be signed - the functionality may need to be built into a compiled application instead.

Greg.

Ok, the nag screen is, for me, a blocker Currently I forward email to tracks, but this right-click option is very tempting, especially because you can change the todo before it is sent to tracks.

Hi Reinier

I have added a section to the wiki page which details how to self-sign the VBA code and remove the macro security warning on startup.

I can’t replicate your other issue - I have installed a clean Windows XP (SP2)/Office 2007 machine and configured the macro there. The Add Todo window opens as it should. I’ll send you a private message with some additional debugging steps to try to isolate the problem.

Regards,
Greg.

Thank! I’ll try it again soon using your instructions.

The script install succeeded and I did get rid of the warning when starting up.
So far so good.

But it has problems with my personal site (or externally hosted ones)
using https as a protocol and proxy authorization.

I Googled and added the following (you need some extra variables!):

Which seems to solve the issue of proxy authorization.

But the certificate on the other site causes problems so the script fails.

Any ideas how to solve this?