My recent newsletter with the screen-cast of the old Windows 3.1 Macro Recorder prompted the following email from long time customer, Ian. In his email he reminisces about how he originally found and used Macro Scheduler to solve a thorny problem for his employer which had previously stumped Microsoft. It’s a good story so I thought I’d share:
I wanted to take a moment to say thank you for the upgrade to Macro Scheduler you sent me this afternoon. I’ve installed it and had a look at the sample scripts – I think I’m going to have fun with the image stuff J
Since it’s been so long, I think I am now able (if you are not bored silly) to explain how I used Macro Scheduler to save the bank a bucket of money…
I joined [large well known international banking group – name removed] as a ‘technical discovery analyst’ in the XP roll out project. No one ever explained exactly what my job was, but it turned out to be ‘sh!t catcher’ – anything that couldn’t be sorted elsewhere ended up on my desk and I had to find a fix (often in less than a day!).
The bank used a well known credit checking agency to do credit checks. In those days [well known credit checking agency] used Security Certificates in Internet Explorer to track billing data – each cert was a unique valuable entity, and we had two options; export them from the machines prior to switching them out, or reissue 10,000 certs! This is the task that Microsoft came in to do (they left about a month before I joined). The problem was that the certs are designed not to be exportable automatically, so that they cannot be programmatically stolen. And so they arrived on my desk.
Since I knew that I had to get a lot of people to run through a complex export procedure (much clicking and saving in the right place), I thought back to the Macro Recorder in Win 3.1. I knew that it wasn’t in NT or 2000 (which was in use at the time) and a quick Google brought me to your site. I popped downstairs to ask my boss for a hundred pounds for a proof of concept (!) and she gave me her bank credit card :-).
Once I had the software installed on my workstation I began to hack through the samples and the manual. By the end of the first day I had a pretty good idea of what I had to do, and at close of play on the next day I had successfully exported and reimported certificates. I was able to go back downstairs and say that I had a viable solution. Much Brownie Points for that conversation!
The export script had 19 versions by the end, and the import one had 11 (the users ran the export first, then the import on their new machine). I’ll attach the last version so you can wince at my cludgy code!
I also wrote a script to find out how much file data was on local machines since it was going to be dumped onto FP servers. That one’s an even bigger bowl of spaghetti code J
Anyway, I’m sure that’s enough for now! Thanks again and I’ll continue to spread the word about Macro Scheduler.
Take care, Ian