I'm a bit stumped here so maybe I could get someone to enlighten me.
I recently threw together a small MS Access database with a lot of help from Lagbolt and Jal here on the forum. (they rock!)
It searches my shared drives and populates a database table with the following information:
File Name
Full path to File
Size of File
Owner of File
Modified Date/Time
It is coded in such a way that I can click the search button and then browse to any drive, local or remote, to scan it.
Here's the conundrum;
If I use the browse function and go through Network Neighborhood, then entire network, then browse to the file server I want to scan, then select the root folder of the share I want to scan, and then start the scan, it takes a minimum of 28.9hrs to complete the scan and populate the table. (we're talking about 585Gb of data on that share that it pulls information about)
If I map that UNC pathname to a drive letter, O: for example, it takes 5.8hrs to completely scan and populate the database.
Why would there be such a huge disparity in scan times? We're talking about 4.982 times longer if I do not map the drive here...
That seems odd, to say the least..."WTF?!" sums it up best, in my opinion.
Any ideas?
I recently threw together a small MS Access database with a lot of help from Lagbolt and Jal here on the forum. (they rock!)
It searches my shared drives and populates a database table with the following information:
File Name
Full path to File
Size of File
Owner of File
Modified Date/Time
It is coded in such a way that I can click the search button and then browse to any drive, local or remote, to scan it.
Here's the conundrum;
If I use the browse function and go through Network Neighborhood, then entire network, then browse to the file server I want to scan, then select the root folder of the share I want to scan, and then start the scan, it takes a minimum of 28.9hrs to complete the scan and populate the table. (we're talking about 585Gb of data on that share that it pulls information about)
If I map that UNC pathname to a drive letter, O: for example, it takes 5.8hrs to completely scan and populate the database.
Why would there be such a huge disparity in scan times? We're talking about 4.982 times longer if I do not map the drive here...
That seems odd, to say the least..."WTF?!" sums it up best, in my opinion.
Any ideas?
