jchd

The string supplied to Execute is AutoIt code, which is then executed. This is the way to execute dynamically created code.

Regex school: Local $text = FileRead(@ScriptDir & "\" & "source.txt") Local $hex = Execute('"' & StringRegExpReplace($text, '(?m)(?<=[[:xdigit:]]{5})([[:xdigit:]])(?=[[:xdigit:]]{2})', '" & _IncHex() & "') & '"') ConsoleWrite($hex) Func _IncHex() Local Static $Inc = 15 $Inc += 1 Return Hex(Mod($Inc, 16), 1) EndFunc I added two extra line in the source file, yielding: X0 00112033 X1 AABBC1DD X2 22446288 X3 BBDDF300 X4 11335477 X5 AACCE5FF X6 11AA26BB X7 CC33D744 X8 55EE68FF X9 ABCD9988 X10 8800AADD X11 EEFF3B44 X12 6622ACEE X13 5599CDFF X14 AAFF2E00 X15 0099AFCC X16 FD5A00B6 X17 10E51194

Never ever store a key, password, login, ... in clear in a program. Store a strong hash of the value, let user enter value, compute its hash and compare hashes.

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.