Received: by 10.66.90.37 with SMTP id bt5mr4409538pab.40.1352149867366;
        Mon, 05 Nov 2012 13:11:07 -0800 (PST)
X-BeenThere: 37signals-api@googlegroups.com
Received: by 10.68.201.133 with SMTP id ka5ls25289436pbc.3.gmail; Mon, 05 Nov
 2012 13:11:05 -0800 (PST)
Received: by 10.68.131.8 with SMTP id oi8mr2523289pbb.15.1352149865789;
        Mon, 05 Nov 2012 13:11:05 -0800 (PST)
Date: Mon, 5 Nov 2012 13:11:05 -0800 (PST)
From: PeterPierce <awd...@gmail.com>
To: 37signals-api@googlegroups.com
Message-Id: <6d271ebf-8032-4ac5-b3f0-25b5ff516ca7@googlegroups.com>
Subject: BC Classic connector for Google Calendar
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_151_13193012.1352149865207"

------=_Part_151_13193012.1352149865207
Content-Type: multipart/alternative; 
	boundary="----=_Part_152_7278999.1352149865207"

------=_Part_152_7278999.1352149865207
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Looking at making an effort to build a connector between our BC company 
calendar and our Google company calendar for bi-directional updates.

This is clearly a major undertaking even for someone with experience in 
both products, but it would move us forward with BC use on many levels.

If someone is already working in this area I'd love to hear about it prior 
to beginning.

------=_Part_152_7278999.1352149865207
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Looking at making an effort to build a connector between our BC company calendar and our Google company calendar for bi-directional updates.<div><br></div><div>This is clearly a major undertaking even for someone with experience in both products, but it would move us forward with BC use on many levels.</div><div><br></div><div>If someone is already working in this area I'd love to hear about it prior to beginning.</div>
------=_Part_152_7278999.1352149865207--

------=_Part_151_13193012.1352149865207--