Re: Current time (*) incorrect today on v17?

Wow! And thanks for the info, no rush on 17.1, for this issue at least! Alan On Mon, Mar 18, 2019 at 9:50 AM Jeffrey Kain via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Our server disconnected all users and stopped responding at the time of > the time change in v17.1. Coincidence? > > > On Mar

Re: Current time (*) incorrect today on v17?

Our server disconnected all users and stopped responding at the time of the time change in v17.1. Coincidence? > On Mar 18, 2019, at 9:42 AM, Alan Tilson via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Just wanted to let everyone know that this is still happening in v17.0. Does > anyone know

Re: Current time (*) incorrect today on v17?

It was supposed to have been fixed in 17.0 HF4. > On Mar 18, 2019, at 9:42 AM, Alan Tilson via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hello out there, > Just wanted to let everyone know that this is still happening in v17.0. Does > anyone know if it is fixed in v17.1? > Thanks,

Re: Current time (*) incorrect today on v17?

Hello out there, Just wanted to let everyone know that this is still happening in v17.0. Does anyone know if it is fixed in v17.1? Thanks, Alan -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet

Re: Current time (*) incorrect today on v17?

> > > This is not only on Mac. We had the same problem on Windows. 64 bit server and 32 bit clients. -- D Samson ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options:

Re: Current time (*) incorrect today on v17?

Hi, timestamp is agnostic to timezone which is why it wasn’t caught by the bug. 2018/11/05 19:14、Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>のメール: So Timestamp uses a completely different -source- for determining time than Current time and Current date?

Re: Current time (*) incorrect today on v17?

All of our customers also had to relaunch their servers yesterday. They are all on v16r6. Must be a new bug as I don’t remember this happening in the past. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 > On Nov 4, 2018, at 12:01 PM, Jeffrey Kain via 4D_Tech

Re: Current time (*) incorrect today on v17?

Miyako, So Timestamp uses a completely different -source- for determining time than Current time and Current date? On Mon, Nov 5, 2018 at 12:45 AM Keisuke Miyako via 4D_Tech < 4d_tech@lists.4d.com> wrote: > 16R4 and later offers Timestamp > >

Re: Current time (*) incorrect today on v17?

> Le 5 nov. 2018 à 09:42, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com > > a écrit : > > 16R4 and later offers Timestamp > > http://doc.4d.com/4Dv17/4D/17/Timestamp.301-3730728.en.html > > >

Re: Current time (*) incorrect today on v17?

16R4 and later offers Timestamp http://doc.4d.com/4Dv17/4D/17/Timestamp.301-3730728.en.html https://blog.4d.com/timestamp-is-now-available/ 2018/11/05 17:40、Arnaud de Montard via 4D_Tech <4d_tech@lists.4d.com>のメール: I'd like to have 4D functions for UTC:

Re: Current time (*) incorrect today on v17?

> Le 4 nov. 2018 à 20:01, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Seems like Current time(*) from a client might be cached incorrectly as an > optimization, since Current time and Current time(*) on the server both > returned correct values. Looks like. But I'm

Re: Current time (*) incorrect today on v17?

for tracking purposes, the ID is ACI0098123. I understand the problem occurs on Windows only, 4D 64-bit only (16R and v17) 2018/11/05 3:54、Christian Sakowski via 4D_Tech <4d_tech@lists.4d.com>のメール: Yes, we (in Europe) has the same issue one week ago, because we gone

Re: Current time (*) incorrect today on v17?

Seems like Current time(*) from a client might be cached incorrectly as an optimization, since Current time and Current time(*) on the server both returned correct values. This completely broke credit card processing until I could track this down. Thanks for confirming that this is a

Re: Current time (*) incorrect today on v17?

Yes, we (in Europe) has the same issue one week ago, because we gone back from DST last Sunday of Oct. However, i reported this issue to 4D (Germany). -- Grüße/Regards, [heubach-media] | Christian Sakowski christian.sakow...@heubach-media.de Tel: +49/(0)40/52 10 59-23 > Am 04.11.2018 um

Re: Current time (*) incorrect today on v17?

> Le 4 nov. 2018 à 18:34, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Looks like restarting the server fixes it. Sorry, I did not see you mentioned v17. For my own I see my alert twice a year since v12: seems to be a deep solid bug. I've heard in Europe Daylight Saving

Re: Current time (*) incorrect today on v17?

> Le 4 nov. 2018 à 17:23, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Is anyone else seeing that current time (*) called from a Mac client to a > Windows server running 4D v17 (HF3) is returning a time that's an hour ahead? > > The Windows time on the server is current,

Re: Current time (*) incorrect today on v17?

Looks like restarting the server fixes it. > On Nov 4, 2018, at 12:29 PM, Jeffrey Kain wrote: > > Yep - everything is in synch as far as Windows is concerned - same time zone, > etc. Same time zone on the Mac as well. Two of our three servers yield the > wrong time on Mac clients (and maybe

Re: Current time (*) incorrect today on v17?

Yep - everything is in synch as far as Windows is concerned - same time zone, etc. Same time zone on the Mac as well. Two of our three servers yield the wrong time on Mac clients (and maybe Windows clients too) when asking for the server time. > On Nov 4, 2018, at 12:26 PM, Jeremy French via

Re: Current time (*) incorrect today on v17?

Are the server and client in the same time zone? In the US the time changed — in the early morning of November 4th — from daylight saving time to standard time. So, do both the server and client computers automatically set the date and time? If not, is the client still on daylight saving time?

Current time (*) incorrect today on v17?

Is anyone else seeing that current time (*) called from a Mac client to a Windows server running 4D v17 (HF3) is returning a time that's an hour ahead? The Windows time on the server is current, and current time on the server returns the correct time. But current time(*) from a client is an