<div>
How are you getting the list of files? &nbsp;If you are using DIR() then I can believe it is causing problems. &nbsp;But if you are using FSO I thought that handled international characters okay. &nbsp;Typically a recursive approach works well, let me know if you need examples, or post your code here and we can suggest adjustments.<br />

<hr />
»<b><i>bp</i></b>
</div>


<div>
Thanks, Bill !!!<br>I did some additional testing. &nbsp;Unless my mind is too groggy, here are the results:<ol><li>With the Dir() and fso.GetFile() statements, the program works until it encounters the problem file.</li><li>I disabled the fso.GetFile() statement and the program navigated through the entire directory structure via Dir() with no problems, even recognizing the problem file.</li><li>I stripped the program down to just the essential lines. &nbsp;I removed the Dir() statements, and the fso.GetFile() used a hard-coded address of the problem file. &nbsp;Surprisingly, it worked fine.</li><li>Then I added the Dir() statement back in, prior to the GetFile() statement with the hard-coded address. &nbsp;The program failed with the same error.</li></ol>This seems to indicate a combination that makes no sense to me. &nbsp;I don't understand the interplay between these two supposedly independent functions.<ul><li>The Dir() and fso.GetFile() statements work together properly if there are NO filenames with international characters.</li><li>When both Dir() and fso.GetFile() statements are present, the fso.GetFile() works on conventional filenames but fails on a filename with international characters.&nbsp;</li></ul>This seems to confirm your proposition. &nbsp;So I guess I need to find an fso equivalent to replace the Dir() mechanism. &nbsp;Below is my logic, stripped to the essentials. &nbsp;The collection drives the recursion down through all subdirectories. &nbsp;Each recursion level creates its own DirQueue collection. &nbsp;It works its way down to the bottom, and then back up again. &nbsp;If you have something that has worked for you, I'd appreciate your suggestion!&nbsp; Merci<br><pre><code class="code-10 nolinks" id="code-20-43085614-1"><span>private function ProcessDir(dirName)</span>
<span>&nbsp;&nbsp;&nbsp;dim DirQueue as new collection</span>
<span>&nbsp;&nbsp;&nbsp;' Iterate through the current directory contents</span>
<span>&nbsp;&nbsp;&nbsp;thisDir = Dir(dirName, vbDirectory)</span>
<span>&nbsp;&nbsp;&nbsp;Do Until thisDir = vbNullString</span>
<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if thisDir is a subdirectory add it to the DirQueue collection</span>
<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if thisDir is a file, use fso.GetFile() to access the attributes</span>
<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;thisDir = Dir()</span>
<span>&nbsp;&nbsp;&nbsp;loop</span>
<span>&nbsp;&nbsp;&nbsp;' After all directory contents are examined, recurse through each subdirectory</span>
<span>&nbsp;&nbsp;&nbsp;for each DirQueue in the collection</span>
<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ProcessDir(DirQueue)</span>
<span>&nbsp;&nbsp;&nbsp;next</span>
</code></pre>
</div>


<div>
Just a comment:<br />
<br />
When doing recursion, ensure that all FSO relevant stuff is done and properly cleaned (set nothing) in your method before executing the recursion call. <br />
Dangling references may cause memory problems, which can also lead to problems, when you have &quot;huge directory structures&quot;.
</div>


<div>
Okay, I'll dig up a sample...<br />

<hr />
»<b><i>bp</i></b>
</div>


Dave Credicott

<div>
Bill,<br>I changed my program to use the fso.GetFolder function, and it looks very similar to your code. &nbsp;Most importantly, it works fine and has no problem handling international characters in the filename. &nbsp;I'm marking your post as the solution, and I greatly appreciate your help!
</div>


<div>
Welcome, glad that was helpful.<br />

<hr />
»<b><i>bp</i></b>
</div>


<div>
<div class="content wysiwyg-content">
I created an Excel spreadsheet to help recursively analyze our huge directory structures, recording directory info (number of files, file types, sizes, date modified, full pathname length, etc.). The file attributes are successfully obtained by either of the subject functions. &nbsp;The output will help us reorganize and migrate network shared drives into the cloud. &nbsp;Therefore, each directory and file must be fully included in the analysis.<br />
<br />
However, when the VBA program encounters a filename with foreign characters, both functions fail with a &quot;file not found&quot; error (see attachments). &nbsp;If I rename the file, changing the accented e to a plain E, the program works fine. &nbsp;I can ignore the error with error handling, but then I don't have the necessary attributes in the analysis. &nbsp;We are an international organization, so there are *plenty* of special characters.<br />
<br />
I cannot find a way to include these files in the analysis. &nbsp;Any help would be greatly appreciated. &nbsp;The environment is Win 10 Office365 Excel 2016 with VBA 7.1.<br />
<br />
Dave<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2020/05_w20/1455930/Problem-File.png" target="_blank" title="Example of failing file (4 KB)"><img alt="Example of failing file" class="file-block lazyload" style="max-width: 603px;" data-src="https://filedb.experts-exchange.com/incoming/2020/05_w20/1455930/Problem-File.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2020/05_w20/1455931/Error-Msg.png" target="_blank" title="VBA Error Msg (11 KB)"><img alt="VBA Error Msg" class="file-block lazyload" style="max-width: 460px;" data-src="https://filedb.experts-exchange.com/incoming/2020/05_w20/1455931/Error-Msg.png" /></a>
</div>
</div>


Error-Msg.png

Problem-File.png

I created an Excel spreadsheet to help recursively analyze our huge directory structures, recording directory info (number of files, file types, sizes, date modified, full pathname length, etc.). The file attributes are successfully obtained by either of the subject functions.  The output will help us reorganize and migrate network shared drives into the cloud.  Therefore, each directory and file must be fully included in the analysis.

However, when the VBA program encounters a filename with foreign characters, both functions fail with a "file not found" error (see attachments).  If I rename the file, changing the accented e to a plain E, the program works fine.  I can ignore the error with error handling, but then I don't have the necessary attributes in the analysis.  We are an international organization, so there are *plenty* of special characters.

I cannot find a way to include these files in the analysis.  Any help would be greatly appreciated.  The environment is Win 10 Office365 Excel 2016 with VBA 7.1.

Dave



VBA errors with GetAttr() and fso.GetFile()

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.