Commentary

Google Tweaks Gmail Calendar Sync

Google first offered up the ability to sync your Gmail and Outlook calendars in early March. Since then, it's received a bunch of feedback on the usability of the product and has decided to make some changes. The changes are welcome, indeed.

Google first offered up the ability to sync your Gmail and Outlook calendars in early March. Since then, it's received a bunch of feedback on the usability of the product and has decided to make some changes. The changes are welcome, indeed.Making sure calendars between devices, platforms, and PCs are all in sync can be a serious pain. Last month, Google sought to lessen some of that pain with its Google Calendar Sync product. Unfortunately, it didn't quite go all the way. Users sent in feedback on a few issues, and Google felt an update was necessary.

The Official Gmail Blog wrote up a brief entry explaining the changes. It said, "Previously, your Google Calendar e-mail address needed to be the organizer or an attendee of your Microsoft Outlook events for the Outlook events to sync to your Google Calendar. Now, when you choose to do a 2-way sync or a 1-way sync from Outlook calendar to Google Calendar, all of your Outlook events will be synced to your Google Calendar."


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This latest enhancement should relieve some frustration of users who were caught in the organizer/attendee web. Google is auto-updating people who use the sync program, but if you're impatient and want to download it directly, you can. The new version is 0.9.3.2.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links