This is posts https://www.excelfox.com/forum/showt...age3#post25028
https://www.excelfox.com/forum/showt...age2#post25032
Some extra notes to go with these main forum post
https://eileenslounge.com/viewtopic....326446#p326446
I am catching up here and responding to some of the interesting info in this post
I might also be responding to the second half of this one , bit I still have not quite figured out what was being said there. ( I wasn't confused by the AidFromGuid metjhopd , - I know that's the SiP syndrone (Smartphone In Pub) :smile: )
Or maybe I am just pondering, a not uncommon occurrence
So… Update so far, and introduction to current stand
Going back a year and / or 4, we have tangled with "Clsid registry lists" before, and the digressions here forced me to revise them again, from and around here , or there abouts.
I had back then a bad Winniemidgetgismo coding, and Mike did it better, (a not un common state of affairs in recent years….)
It ended up like this
https://i.postimg.cc/Y9Q7rPYQ/Old-Clsid-Lists.jpg
The coding that got the lists…
What I tried was I Initially got just the Clsid list and then, a while later, I tried to stick them pseudo in a
Obj = CreateObject("New:" & MeClisid & "")
, see what happened. It did not damage or break too much on my computers, at last not all of them always, but I was not too sure what was going on. If an attempt did not error or break something, then I did a
TypeName(Obj)
, on the resulting object. I am not sure why I did that, I expect I just thought at the time that somebody perhaps should. I had no idea what the results were telling me.
You ( You= Mike ) in your coding equivalent got both the Clsid list and a ProgID. (And as I understand a bit better the winygismo codings I know now where that came from). Your code never errored or broke things like mine did, and there were sometimes similarities with your ProgID results and my TypeName(Obj), for the same Clisid
https://www.excelfox.com/forum/showt...ll=1#post25010
https://www.excelfox.com/forum/showt...ll=1#post25012
CLSDsUndClassNames.xls - https://app.box.com/s/nkjwti5yym9j0v634hrxerz4x7n1o90w
But I was still none the wiser on what it all meant..
But I am getting there now…
So lets look at your current example : https://i.postimg.cc/NMvg1Dw0/Little...ng-Runtime.jpg https://i.postimg.cc/7hD0QSSH/Micros...e-adding-a.jpg This is whre we might fist come across it, when "checking a reference for Early Binding"
We have learnt now that the relevant word to use there is the "human readable description" or "TypeLib human readable name", aka the name to look for in the little window for checking a reference
, - and here it is in "the Clsids" file of mine from s few years back
https://i.postimg.cc/05f8w7X8/Clsid-...ng-Runtime.jpg ,
{0D43FE01-F093-11CF-8940-00A0C9054228} Tried FileSystemObject {0D43FE01-F093-11CF-8940-00A0C9054228} Scripting.FileSystemObject
Here we can see it again in the little reference checking VB Editor window, https://i.postimg.cc/NMvg1Dw0/Little...ng-Runtime.jpg, but that is perhaps not coming from directly from there, well maybe it is sort of,….
This is something new we picked up, Here it is (a different Guid number note), in the Registry Hive HKEY_CLASSES_ROOT , at the path TypeLib\{420B2830-E718-11CF-893D-00A0C9054228}\1.0
https://i.postimg.cc/J01MFh0V/Reg-Ty...ng-Runtime.jpg
And we got some more recent Winnie codings to get that TypeLib info
{420B2830-E718-11CF-893D-00A0C9054228} 1.0 Microsoft Scripting Runtime
So that is a refresh on the Clsid stuff, and a bit extra about the TypeLib Guid
( This is also the Guid used in the .AddFroGuid – We do mot use the Clsid Guid there! )
Now we will move on in the next post
Reply With Quote
Bookmarks