You could certainly check for all these formats - I'd check for each in turn. However you are not always going to distinguish between DD-MM-YYYY and MM-DD-YYYY or DD/MM/YYYY and MM/DD/YYYY. If the day is less than 13 you have no way of knowing which one it is.

Thanks for your post. Many people have come to Macro Scheduler with no programming background and then moved on to using full featured/traditional programming languages, so you won't be the first to move on. It has always been a stepping stone for many. The core purpose for Macro Scheduler has alway...

I'm sure you can. It's not going to happen though. There's no way we can maintain a context aware PDF file and build that into the software. If 75% of our customer base had no internet we might consider it!

No, CHM was deprecated years ago. WinHelp is also no longer provided by Microsoft. While it _may_ be possible to make it work with sufficient old unsupported libraries it means a lot of extra bulk and that's before the size of the help itself - Macro Scheduler's help is large. But we also have to ma...

The "Results" variable isn't populated as expected (that would be a string with "name=value" pairs). So that actually has nothing to do with the HTML viewer object and is in fact because the parameter type of the Results parameter is a string list which Macro Scheduler doesn't know about. However, ...

Wow. It's the Microsoft WebBrowser control which is part of Windows. TMS stands for Type Macro Scheduler - TWebBrowser becomes TMSWebBrowser, etc. It has nothing to do with TMS Software whoever that is. It supports Javascript. If you want to automate a browser we have Edge/Chrome functions for doing...

GetWindowChildList is now part of the gutter but missing in the "Code Builders" panel (or am I really blind?). It is there, defined in comdef.ini but we don't overwrite your comdef.ini on upgrades as you may have favourites etc set up. I know the new dialog objects are experimental but shouldn't we...

I got PDF XChange installed and when I load a local pdf for the tMSWebBrowser object (URL property) the PDF-XChange interface is showing up. Pretty great if you ask me :) Not sure if this part of the scoop? All depends how your system is configured, what IE plugins you have and how they are configu...

Please update to 15.0.26 just released today which should fix this.

I can't replicate. Same macro, run from top always runs from top, no matter which line I have selected.

Will look to see if we can improve it so that ONERROR works for complex expressions in If statements

Sorry, presently complex expression errors can be set to be ignored with LET>IGNOREERRORS=1 but not captured.

So the error is from an undeclared string variable in a complex expression. I would make sure those variables are initialised. However if you set IGNOREERRORS to 1 and set an error handler with ONERROR as you have done then any errors inside a complex expression should jump to your ONERROR handler. ...

I don't think the issue is with If. the issue looks to be that the LibFunc failed and as such the parameter list didn't get constructed. I think the only sensible solution is initialise the variables before calling LibFunc. Then check them after and also check the main return variable of LibFunc.

I'm afraid since a PDF is not an image format it won't be possible to display one via an image object. So some other object/method would be required. We will investigate options.