This is post#post23769
https://www.excelfox.com/forum/showt...age2#post23769
https://www.excelfox.com/forum/showthread.php/2936-YouTube-Video-making-and-editing-etc-coupled-to-excelfox-(-windows-Movie-Maker-)/page2#23769
Some macro refinements: Improved accuracy of Property values
Recap: The windows shell object folder items way
This is potentially a nice ordered way. If all the properties worked it would be great. It seems to have worked well up to XP, but after that both the order of properties listed changed and more and more of them broke. In addition some numbers, in particular size, when working are in some less precise, perhaps rounded KB or MB number, whereas if it is given in a Bytes number, then it appears to be a more precise figure.
( The different size numbers available can also be seen together if you look at a file or folder manually via the Right click --- Property way, https://i.postimg.cc/DwnT0hy7/Movie-...erties-way.jpg
https://eileenslounge.com/viewtopic....313555#p313555 Movie Maker 2 Properties from Right Click --- Properties way.jpg )
So, looking in particular at the size, issue, but also generally at the file and folder property issue, I took a time out to see if I could come across some other ideas to get properties , for example with this forum post
https://eileenslounge.com/viewtopic....313622#p313622
https://eileenslounge.com/viewtopic....313559#p313559
The TLDR outcome of all that is that I will stay with the windows shell object folder items way but also use at some points the Microsoft Scripting Runtime Library way, (commonly also referred to as the FileSystemObject(FSO) way), to get an accurate value of size.
Here is a simple test file to demo what I mean: https://www.excelfox.com/forum/showt...ll=1#post23924 this appears initially to give satisfactory results.
More detailed conclusions and discussions
Some concluding thoughts
File Size: accuracy , or rather the value for Alan to use for the purposes of comparing files that may be similar or the same.
At the moment I am firstly interested into getting some consistent results, preferably not rounded, to compare files that are similar or the same. In terms of size, numbers given vary for a particular file, (or folder) , and I have come to the conclusion its best not to ask anyone about converting a Byte to KB or MB or visa versas. If you do ask, then it’s time to hide in a nuclear fallout shelter for a few months, and wait until world war 3 is finished fighting over it. It seems to be down to what definition is your God that you would fight to death for.
The best I can say is that if, as in my used example so far, I see figures for the same file of 628 KB, 629 KB and 647168 Bytes, then it is likely that some rounding has gone on those KB figures so the Byte figure is the best one for my purposes? I would welcome any comments on just this last statement, I mean does it sound a good idea to take, in such a case the 647168 and not worry too much about the other KB or MB number?
_Ways to get the size ( and some other properties maybe )
At the outset of the little project this is related to, I was not so sure what properties I wanted, so after I caught Microsoft Shell Controls And Automation way (windows shell object way) , I thought great , that’s a pretty full list. Unfortunately by every new Microsoft operating system version both the list order and available properties has changed, and progressively more and more of the property values don’t work – it’s become more broken as time went on. Because of this and because I was narrowing down the list of properties to use, I started looking at other ways.
Conclusions so far about getting the size, and perhaps a few other Properties, comparing the ways
_Built in VBA way, and the VBA Open For Input LOF(1) Close way
I will take a wild guess these two use the same low end coding somewhere. They both give the nice Byte number. But they only work for files. There are not many other properties to get in these ways either
_Microsoft Shell Controls And Automation way (windows shell object way, (WSO))
A bit broken and inconsistent as time goes on, but using this in XP can give some other properties that I can’t seem to get in any other way. For a file we have a couple of ways within the Microsoft Shell Controls And Automation way (windows shell object way). The Item.Sizeproperty gives the nice long figure Byte number, and the objFolder.GetDetailsOf(Item, 1) gives the shorter KB or MB figure, which I presume is rounded. It appears that if the item is a folder, then both these size things are broken, even as far back as XP. The size property gives zero and the GetDetailsOf method
(I note that in any explorer window I have ever seen the folder property never works. I don’t know if there is any connection there?)
_ This seems to be the only way so far to get me a folder size programmatically with VBA. The file size given is the nice full digits Bytes, as it is also for the files size. So this might be the one to use for size
_._______________
So for the time being, in ouder to move on, the macro so far, the recursion / reoccurring one will be modified a bit, mostly to get the accurate and working size property given by the WSO way
See around
https://www.excelfox.com/forum/showt...s-etc-)/page17
https://eileenslounge.com/viewtopic....313792#p313792
https://eileenslounge.com/viewtopic....313792#p313792
https://www.excelfox.com/forum/showt...s-etc-)/page18
Reply With Quote
Bookmarks