cproc | C11 compiler | Parser library

I wouldn't recommend using IE for automating VBA form submission.

Here's my experience: You spend a lot of time trying to solve this kind of 'what happened the click was supposed to work' errors. Or why did the page not load all the way errors? or how do I wait for the page to load and click what it needs.

TBS: having spent too much time trying to make this sort of thing work, and oftentimes getting a good result. I'd suggest using your DevTools (f12 in IE) while on the page. First click the button normally and see what happens. Next Click the button using JavaScript run in the console section. It'll be something very similar to your click syntax. Take note of what element is actually being clicked by using the inspector in dev tools and what script is running with the event.

IE does have ways to run the exact javascript on the page, you might need to replicate the form click event and javascript using this syntax:

In your Python example, no shell is involved: Python executes cp directly. Globs are only expanded by the shell, so cp receives the literal argument /Volumes/Data/abcd/aging_logs/boards/*.log and no file with that name exists.

In the scp case, the * is being passed literally to scp in the same way, but scp is expanding the glob on the remote system. This is a feature of scp.

You can use the glob module to expand the glob and pass the full list of filenames to cp. (You could also use Popen's shell=True argument, but please heed the security considerations in the documentation.)

The critcl code isn't very sophisticated when it comes to type mapping; it's just lowering the arrays to pointers to arrays and that's just not very nice for you, especially as it doesn't enforce the number of elements in the arguments. In this case, you're best doing it yourself.

Note that we need to also pass in the interp special and return the ok special “type” (so we can do error reporting), and we use the Tcl_Obj* type for the arguments, which disables (virtually) all the type mapping.

This could be due to the fact that another error with another error number is raised while the macro runs. To avoid missing this error, you can add a different message if the number is not the one you want.

How about:

I would forgo the use of the Scripting.Dictionary and simply keep a reference of the latest CreationDate: