I don’t own a Mac and nor can I get VirtualPC to emulate one properly due to my PC using an AMD processor.
So my thanks to John Espirian for all of his help last Friday as I kept sending versions of the toolkit to him for testing on his Mac. Each new beta version had some minor tweaks applied which (in my head) should have enabled the toolkit to work. But he kept getting errors each time he ran it – the only thing that worked ‘out of the box’ was the Which Fonts? routine.
Apparently it’s my use of the GetSetting command in VBA as it works differently on a Mac as it does compared to Windows. Under Windows, your settings are stored in the Registry. On a Mac they are stored inside a file within the System area – well, that’s as far as I understand it.
I’m thankful that Ron de Bruin’s website has been very helpful in giving some hints and tips about how the ‘GetSetting’ command works differently on a Mac, compared to how it does under Windows and I should (fingers-crossed) be able to get it working fairly soon. This is because the Infrastructure department where I work are going to loan me a MacBook for a few days (along with Office 2016) so that I can try and work out why code breaks.