Re: Video viewer on Webarea on Windows 7

Hi, (I don't see a name sorry). I am using URL's and they work on Win7 on Chrome but not Explorer. So certain it's not a URL problem. It may be the Webkit use so I'll check that. I've disabled drag and drop so I'll try that as well. Thanks for the tips. Cheers Jim Labos - infobase - Jim

4D v16.4 Built database won't open in Mojave

Folks, I have built a stand-alone Application v16.4 database on a Mac OS machine running High Sierra (10.13.6). I successfully create an empty datafile and run it on the same High Sierra (10.13.6) machine. I transfer the entire stand-alone built database to a laptop running Mojave (10.14). W

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: Moving picture resources from one database to another

is it not the architecture, not version, that determines whether the conversion would work? a 32-bit version of v17 is available for compatibility, if you go directly to the download site (i.e. not the web site) 2018/11/04 14:24、Robert ListMail via 4D_Tech <4d_tech@lists.4d.com>のメール: This works

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 widespread

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 17:23

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 Tim

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, and

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 hou