jchd

After 18 years, all of them are dead or alike.

I don't know why. It would take to dig inside the source code to find the answer, or maybe ask on their support forum (if any). None of the win64 versions installs correctly here.

Post edited: I did see the * -1 part (and didn't expect it), just the > 0 caught my (olding) eyes.

@Deye you got the comparison wrong: if a match is found, the index of the found array element is returned, which is >= 0, else no match returns -1, which as you know is < 0. EDIT: sorry I looked too fast, focussing on the > 0 only. My bad.

Read the documentation about these two functions.

returns local timestamp.

For resultset with only one column and more than one row, use _SQLite_GetTable() For resultset with more columns and more than one row, use _SQLite_GetTable2D() Forget _SQLite_Query and friends.

There is no such thing as an UTC marker! The letter Z sometimes found at the end of a timestamp means "Zulu", for Zero. The time before is both UTC and local in timezone +0 (they are equal). BTW, Greenwich is to be forgotten, speaking of time. GMT has no more any reasonable meaning since 1972-01-01. Use UTC instead.

1) The SQL you use is the same number of words in your question. The SQL seems quite readable to me. 2) What if you read the SQLite documentation? https://www.sqlite.org/index.html 3) Yes. You ask for one row, so get one row.

That's not reliable (VPN or ISP not under exact same rules) nor enough. Even a GPS location doesn't tell you which rules are in force, even less which rules to use elsewhere in some future. Look at how fast all those things change: https://time.is/fr/time_zone_news

I never used the TaskScheduler.au3 UDF but it should store event datetime stamps in UTC, without any offset. The task should trigger when the PC UTC clock matches that of the scheduler, period. Exactly like what @argumentum posted while I was typing. UTC is the same for everyone everywhere on Earth and anytime. Of course if you move your laptop from one timezone + DST rule to another area having another set of rules, without telling your PC that the local rules have changed, then the bell will ring at the wrong time. Contrary to a laptop, a smartphone connected to a local GSM network knows when you change location and hopefully adjusts the local parameters to where you go.

That is urban legend. Coriolis force is way too weak to impact water in a sink.

DST has nothing to do with North, South, East or West. DST is decided by the rules in force in the country/region/city and the timestamp you consider. This where DST details are available. This timestamp format is not UTC, it is local time. The last part (-05:00) indicates the shift from/to UTC. You must subtract this value to get UTC. This exemple is = 2024-09-28 19:20:55Z

This information has nothing to do with hemispheres! _Date_Time_GetTimeZoneInformation() is your friend.