Re: Enterprise Replication (CDR) and Day light saving.

ER uses the output of the time() function to evaluate the time of the transaction. It does not use localtime(), or ctime(). You should be using the correct TZ variable in you system so that you don't have to manually change the time, but instead the system automatically changes it. On most systems internal time that is returned by the time() function is not affected by timezone. Rather the interpretation of the output of time() is changed. This is why ER can use timestamp conflict resolution across time zones. The output of time() is defined to be the number of seconds since Jan 1, 1970 Universal Time. Universal Time is defined to be GMT+0. Since GMT does not have daylight savings, the output of time() should not be affected. HOWEVER---- If you are using NT on 7.2, then there is an issue if you are using a timezone that does not have daylight savings. This is because there was a problem in the Microsoft libc.lib time functions in VC++ 4.0 that cause the output of time() to be incorrect. This caused a lot of problems with the Eastern Hemisphere locations. Stephen Manga wrote: > Replication Gurus (including Madison), > > This is the first time I have struck daylight saving since starting > replication. > > What is the procedure for changing the clock when running replication? > > Down here in the southern hemisphere we are changing our clocks forward one > hour on Sunday. > > What do we do when changing the clock forward? > > What do we do when changing the clock backwards? > > TIA > > Regards, > > Stephen