|
|
Saving Incorrect time into database
Posted: 24 Aug 06 11:48 AM
|
fiogf49gjkf0d We recently converted to 6.2 from 6.1 ( don't know if this is related to this issue). The problem I am having is as follows: When writing a record into the database, the createdate and modifydate is 5 hours ahead of what it realy should be...
... I have traced the code to the point just before the call to the objRS.Update and the time looks fine (what it should be).
... I have also, duplicated the same functionality in Query Analyzer and found no problemthere...
Thanks in advance for your help! |
|
|
|
Re: Saving Incorrect time into database
Posted: 24 Aug 06 12:37 PM
|
fiogf49gjkf0d I don't believe the problem is with your database. From 6.1 to 6.2 Sage added a bunch of time zone stuff to the system. This is part of the upgrade process. Did you run the GMT Conversion? It's been awhile since I've done it myself but I believe it's in that process that you set your local time zones for each user. Each user has their own time zone so that offices spread through-out the country (countries) can pass the system times that are correct for their location.
If you did not run the conversion at the time of upgrade you can go to C:\Program Files\SalesLogix on your administrative console and open the SLXTimeZones.exe to set your time zones. It can only be run once.
The only way I know of to change the Time Zone for each user at that point is to manually edit their TIMEZONE field in the database (Table name: USERINFO).
If anyone else has a different/better answer I'm interested also. There should be an easier way to change this, like if an employee transfers offices or moves.
Marc |
|
|
| |
|
Re: Saving Incorrect time into database
Posted: 24 Aug 06 1:01 PM
|
fiogf49gjkf0d A better reply than mine I might add. And here I thought I was pulling my weight for once answering instead of asking |
|
|
| |
| |
|