Community
Showing results for 
Search instead for 
Do you mean 
Reply

Conversion from Act2011Pro to Act2012Premium causes a timechange

Copper Elite Contributor
Posts: 193
Country: Belgium

Conversion from Act2011Pro to Act2012Premium causes a timechange

Same machine, 1 database.
Database is changed from Act2011 Pro to Act2012 Premium

All dates are shifted with 1 day earlier.
We are in timezone Belgium (GMT+2) in summer, GMT+1 in winter.
This is the second database in this week i encounter the same problem (the first is from Act2005 to Act2012)
Is there a short remedy for this inconvenience ?

Daniel Dendooven
Retired Act! Certified Consultant
Copper Elite Contributor
Posts: 193
Country: Belgium

Re: Conversion from Act2011Pro to Act2012Premium causes a timechange

Has anyone had the same problem?

People are npw borned the day before !!!!

Customer is not amused.

Daniel Dendooven
Retired Act! Certified Consultant
Platinum Elite Contributor
Posts: 6,668
Country: USA

Re: Conversion from Act2011Pro to Act2012Premium causes a timechange

That problem is typically caused by the computers reagional settings. Every date in MSSQL has a time component and if it isn't used or specified it defaults to 12:00 AM (Midnight). Changing the computer regional settings can cause the date to shift because ACT! records the time as zulu with an offset.

Roy Laudenslager
ACT! Certified Consultant
ACT! Report Expert
Durkin Impact Report Designer
www.techbenders.com
royel@techbenders.com
541-343-8129
Copper Elite Contributor
Posts: 193
Country: Belgium

Re: Conversion from Act2011Pro to Act2012Premium causes a timechange

Problem is that this conversion happened on the same machine, so the time zone (and this user has only 1 (little country you know), so this should not happen !!

The only thing where i can think  on,- and in this case we have to talk about a bug - is winter and summer time, which is there for 6 months.

Solution ?

Daniel Dendooven
Retired Act! Certified Consultant