An update to the popular add-on for ACT! 2007 - 2009 (versions 9 - 11), the new vCard Utility not only sends contact information by automatically attaching a vCard to Outlook, it now Saves to File… vCard information, and Imports a vCard into ACT!, creating a new contact record.
More information can be found at http://www.rbrdatasolutions.com/products.htm
Thanks!
26 October 2009
06 October 2009
Time Zone and Scheduling Activities
Often ACT! users either share, or synchronize information with other users across different time zones. How do you schedule a conference call with 5 people in 3 different zones? What happens when you send an activity email, or calendar invitation to another user?
Luckily, this is something ACT! takes care of automatically, and you don't need to worry too much about it. ACT! stores times in UTC (Coordinated Universal Time), or GMT (Greenwich Mean Time). Basically, ACT! will store the GMT time, and the localization preferences on your computer will determine the time zone (TZ) offset. In short, based on your computer settings, the ACT! program takes the data (date & time in the database), converts and displays it correctly for you, and any other users to see.
How does this work in action? Let say I have a conference call Friday, October 7th at 11:00am. I put that on my ACT! calendar at *my* time, not converting or adding time zones of the other users. However, if you open the hood and look into the database, you will see the time stored as 2009-10-07 18:00:00 So, if I synchronize with a user/server in another time zone, that date is *still* stored as 2009-10-07 18:00:00 ACT's back-end database (SQL Server) does not care what TZ the computer is in, it's up to the ACT! program itself to convert and display the date correctly. Now, when the user accesses that data on their computer, ACT! automatically converts it to their local time. If they are in Boston (go Sox!), they will have a conference call scheduled at 2:00p, on October 7th.
Sending an Activity eMail, or a calendar file invitation works the same way. Although I can't help if someone in Boston schedules an 8:00am (EST) conf call for colleagues in California (5:00am PST), I do hope this helps you use ACT! more efficiently.
Note: There is one caveat to this system. If you are in one time zone (e.g. CST) scheduling *for* someone in another (e.g. EST), you *will* have to take that into account. i.e. If someone in Pennsylvania specifically says "schedule a meeting for 9:00am", you will need to add it on your computer at 8:00am if you're in CST, 6:00am if you're PST, and so on. When ACT! syncs, they will now have an appointment for 9:00am.
Luckily, this is something ACT! takes care of automatically, and you don't need to worry too much about it. ACT! stores times in UTC (Coordinated Universal Time), or GMT (Greenwich Mean Time). Basically, ACT! will store the GMT time, and the localization preferences on your computer will determine the time zone (TZ) offset. In short, based on your computer settings, the ACT! program takes the data (date & time in the database), converts and displays it correctly for you, and any other users to see.
How does this work in action? Let say I have a conference call Friday, October 7th at 11:00am. I put that on my ACT! calendar at *my* time, not converting or adding time zones of the other users. However, if you open the hood and look into the database, you will see the time stored as 2009-10-07 18:00:00 So, if I synchronize with a user/server in another time zone, that date is *still* stored as 2009-10-07 18:00:00 ACT's back-end database (SQL Server) does not care what TZ the computer is in, it's up to the ACT! program itself to convert and display the date correctly. Now, when the user accesses that data on their computer, ACT! automatically converts it to their local time. If they are in Boston (go Sox!), they will have a conference call scheduled at 2:00p, on October 7th.
Sending an Activity eMail, or a calendar file invitation works the same way. Although I can't help if someone in Boston schedules an 8:00am (EST) conf call for colleagues in California (5:00am PST), I do hope this helps you use ACT! more efficiently.
Note: There is one caveat to this system. If you are in one time zone (e.g. CST) scheduling *for* someone in another (e.g. EST), you *will* have to take that into account. i.e. If someone in Pennsylvania specifically says "schedule a meeting for 9:00am", you will need to add it on your computer at 8:00am if you're in CST, 6:00am if you're PST, and so on. When ACT! syncs, they will now have an appointment for 9:00am.
Subscribe to:
Posts (Atom)
