Windows Explorer (and FSO) doesn't know how to reliably count files and subfolders - other options?

[nikos]

"Michael Herman (Parallelspace)" <mwherman@parallelspace.net.no#$#spam>
wrote in message news:Ozw2NkyREHA.1392@TK2MSFTNGP09.phx.gbl...

> The folder properties dialog in Windows Explorer and the FileSystem object
> both on a Windows Server 2003 system doesn't provide accurate counts of

the

> number of files and subfolders in a parent folder.
>
> This is a huge suprise to me that the Windows Explorer folder properties
> dialog is unreliable.
>
> When the length of a file path is at or near the maximum length of 248 for
> the file path and 260 for the fully qualified path name, Windows Explorer
> produces a garbage number that can be off by thousands of files.
>

as always, a simple workaround is to use FindFirst/Next but using the 8.3
version of the pathnames so that you never exceed the 260 chars limit

GetShortPathName may help but itself has a limit of 260 chars, so you may
need to write your own

---
[url]www.netez.com/2xExplorer[/url]

[Michael Herman \(Parallelspace\)]

It's extremely odd that in the current Windows o/s that there isn't a
trustworthy way of getting an accurate count of the files and subfolders in
a parent folder.

Michael.

"nikos" <umeca74@hotmail.com> wrote in message
news:%23Y5lEANSEHA.556@TK2MSFTNGP10.phx.gbl...

> "Michael Herman (Parallelspace)" <mwherman@parallelspace.net.no#$#spam>
> wrote in message news:Ozw2NkyREHA.1392@TK2MSFTNGP09.phx.gbl...

> > The folder properties dialog in Windows Explorer and the FileSystem

object

> > both on a Windows Server 2003 system doesn't provide accurate counts of

> the

> > number of files and subfolders in a parent folder.
> >
> > This is a huge suprise to me that the Windows Explorer folder properties
> > dialog is unreliable.
> >
> > When the length of a file path is at or near the maximum length of 248

for

> > the file path and 260 for the fully qualified path name, Windows

Explorer

> > produces a garbage number that can be off by thousands of files.
> >

>
> as always, a simple workaround is to use FindFirst/Next but using the 8.3
> version of the pathnames so that you never exceed the 260 chars limit
>
> GetShortPathName may help but itself has a limit of 260 chars, so you may
> need to write your own
>
> ---
> [url]www.netez.com/2xExplorer[/url]
>
>

[Michael Herman \(Parallelspace\)]

robocopy from the Windows Resource Kit appears to be the only Microisoft
tool that provides a trustworthy count of the files in a hierarchy of a
parent folder.

Use the /L option to cause robocopy to run without actually copying
anything. This is the fastest way to get the stastics produced when
robocopy finishes.

Michael.


"Michael Herman (Parallelspace)" <mwherman@parallelspace.net.no#$#spam>
wrote in message news:Ozw2NkyREHA.1392@TK2MSFTNGP09.phx.gbl...

> The folder properties dialog in Windows Explorer and the FileSystem object
> both on a Windows Server 2003 system doesn't provide accurate counts of

the

> number of files and subfolders in a parent folder.
>
> This is a huge suprise to me that the Windows Explorer folder properties
> dialog is unreliable.
>
> When the length of a file path is at or near the maximum length of 248 for
> the file path and 260 for the fully qualified path name, Windows Explorer
> produces a garbage number that can be off by thousands of files.
>
> Same issue with the Filesystem object.
>
> What tool can we use to get an *authoritative* count of the number of

files

> and subfolders in a parent folder? robocopy is the only utility that

seems

> to provide an accurate number.
>
>
> --
> Michael Herman
> Parallelspace Corporation
> Developers of Advanced Business Collaboration Solutions for Microsoft
> SharePoint, Microsoft Live Communications Server and Groove Workspace
>
> Portal and Content Migration Solution Specialists:
> [url]http://www.parallelspace.net/sharepoint[/url]
> SharePoint Migration Knowledge Center:
> [url]http://groups.yahoo.com/group/sharepointmigration[/url]
>
>
>
>

[Torgeir Bakken \(MVP\)]

Michael Herman (Parallelspace) wrote:

> robocopy from the Windows Resource Kit appears to be the only Microisoft
> tool that provides a trustworthy count of the files in a hierarchy of a
> parent folder.
>
> Use the /L option to cause robocopy to run without actually copying
> anything. This is the fastest way to get the stastics produced when
> robocopy finishes.

Hi

Info and download link for the latest version of robocopy.exe here:

[url]http://groups.google.com/groups?selm=4036844E.EF9F733A@hydro.com[/url]


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
[url]http://www.microsoft.com/technet/community/scriptcenter/default.mspx[/url]