I like the first one better. :laugh: I was expecting to see some horrid error-prone mess.

raddevus wrote:

while (!sourceSubFolders.atEnd()){ sourceSubFolders.moveNext(); // do something with files in the folder }

Classic! The proposed rewrite skips the first item. Well, I think we've all been there. ;) Hey, remember this ugly beauty from System.Runtime.Remoting?

static StringBuilder vsb = new StringBuilder();
internal static string IsValidUrl(string value)
{
if (value == null)
{
return "\"\"";
}

vsb.Length= 0;
vsb.Append("@\\"");

for (int i=0; i

The difference between a programmer and a software engineer is how many times you need to read the manual? I thought the difference was around $20,000.

Are you claiming that MS Access performs/runs faster than .NET application doing the same thing? I don't agree with you on that. In my experience, Access processes ran significantly slower compared to .Net equivalents. Unless you meant the time to develop/implement -- for example, whiping up a front-end app, I think you have point in which creating an acesss front-end typically takes less effort than a .Net front-end.

Here's a link to the Microsoft reference source for that specific function - IsValidUrl() :) Reference Source - IsValidUrl(string)[^]

adventofcode.com will begin tomorrow.

Liberation Mono