After using OggSync for ten days, as reported in my previous post, I believe I can say that my complete PIM syncing solution works pretty well. I haven’t had any problems with OggSync, actually, even though I’m using the beta version. It’s installed on home computer, work computer, and on my Windows Mobile 6 phone, and all of them sync to Google Calendar, using two different calendars; one for private and one for work. Both are synced to the home computer and the phone. Have a look at my previous post for the complete syncing solution, using LapLink PDAsync and Windows Mobile Device Center (the ActiveSync of Vista). As a bonus, I can sync my contact list with Gmail, too!
Now I’m trying OggSync for syncing my calendar. The professional subscription wasn’t that expensive, and a colleague of mine was using it without problems, so I’m giving it a try. Works well after two days’ of use!
So, now I’m syncing my two Outlook calendars with Google Calendar using OggSync (different calendars for private and work), my mobile phone directly with Google Calendar using OggSync, my tasks and contacts for my work computer using LapLink PDAsync (contact sync in OggSync doesn’t support categories), and tasks, contacts and notes for my home computer using Windows Mobile Device Center (Vista’s ActiveSync). What a mess! I haven’t found a better (that is, working) combination, though.
I’ll be back with a review later of whether this works over a longer period of time or not. My feeling is that OggSync is very stable indeed.
In a previous post, I suggested that I’ve found a syncing solution that works for syncing tasks, calendar and contacts involving a PDA, a work computer and a home computer, so that I can filter out what items are synced to my work computer, while all items exist on my PDA and home computer. Unfortunately, today I ran into the same problem that I had initially, when I tried to use LapLink PDAsync for syncing to both computers, although now I use it only between the work computer and the PDA (for the filtering functionality).
So unfortunately, I can’t recommend that solution anymore. I’ll be back when I find something better, or a manageable workaround.