05-01-2009 02:17 PM
Corporate environment running in a Citrix environment
ACT! 2007 Premium for Workgroups (22.214.171.124 Hotfix 3)
Databases are stored and shared on a network server located in the Central time zone
Users are located in multiple time zones
Users local machines are configured for their specific local time zone
Databases are maintained (back-up and repair) nightly
Contact records viewed by users in the Central time zone display the birthday correctly (e.g. 7/27/1969)
The same contact record viewed by users in the Pacific time zone display the birthday one day earlier (e.g. 7/26/1969)
Using SQL 2005 Management Studio, the exact date stored in the database is 1969-07-27 05:00:00
This issue does not occur in all databases (just one at this time that we are aware of)
Any ideas on why this may be happening would be greatly appreciated.
05-02-2009 05:34 AM
This is a known issue, annual events are calculated in GMT based on the server location.
During Standard Daylight times
CST = GMT -6 hours
PST = GMT -8 hours
So at 12:01 (AM) on 7/27/1969 CST ACT calculates the event as 10:01 (PM) on 7/26/1969 PST
This behavior is adjusted correctly when using a remote (synchronized) database.
05-02-2009 12:11 PM
Thank you very much for the response.
The users of this database are located in the Pacific time zone. I imported the data on a system in the Central time zone. I see that the values stored in the databae are 5AM.
Could this be resolved if the time of the stored value were adjusted? Possibly setting them to be 12PM?
05-02-2009 01:56 PM
05-04-2009 08:26 AM
Based on the information provided below and further research & testing...
All of the dates for contacts that were imported by me in the Central time zone had a time stamp of either 5AM or 6AM.
All of the dates for contacts that were entered by users in the Pacific time zone had a time stamp of either 7AM or 8AM.
The one hour difference in time was determined by whether the date was during daylight savings time or not.
To resolve the issue, I added 2 hours to all of the dates with time stamps of 5AM or 6AM.
In the future, when I import data for users, I will set my system to be the same time zone as the users before performing the import.
Hopefully this issue will be resolved in a newer version.
Thanks to Brad (realtimeact) for the assistance.
10-29-2012 11:49 PM
This issue is still going on on version 2012.
Updating from version Act!2008 to Act!2012
Customers are working only in 1 time zone.(Europe - Brussels)
After updating same thing with the dates.
Surething this has todo with winter/summertime shifiting
Solution is indeed to change the birthhour.