Dir.RecursiveFindFile

[gbison]

Hey guys,

As the subject states Im having a little trouble with this function. I have used it several times throughout my program with ease, but when using it for an ENTIRE drive (C:\) search for different images(*.jpg, *.png and *.bmp), it makes the program unstable (unresponsive) while its creating its list. It does in fact work as intended if you wait long enough, but its giving the perception that the program is locked up, when in fact it is not. Is there a better way to do massive file searches that has less impact on the program?

Thanks

Bryan

[Slowdown]

Hi Bryan,
to compare,
HD: 900GB with 582407 files
searching entire drive for *.jpg will take 4 minutes, 30 seconds with 15148 files found.

[berndnoetscher]

Hey guys,

As the subject states Im having a little trouble with this function. I have used it several times throughout my program with ease, but when using it for an ENTIRE drive (C:\) search for different images(*.jpg, *.png and *.bmp), it makes the program unstable (unresponsive) while its creating its list. It does in fact work as intended if you wait long enough, but its giving the perception that the program is locked up, when in fact it is not. Is there a better way to do massive file searches that has less impact on the program?

Thanks

Bryan

I would use Dir.RecursiveFindFile together with DoEvents, but instead of search C:\, I would create a list of sub directories of C:\ and use them in a loop together with DoEvents and Dir.RecursiveFindFile.

[Slowdown]

Best solution of both world is use as less as possible DoEvents() if speed is the most important for the app.
drawback is the the app will be less responsive.
Also don't update the tree-listview after each file found, this consumes time.
For instance update after each directory.
Did also a test with Q7B and have to say it's a bit faster.
(i know what the project is)

[gbison]

Thanks both of you....

@slowdown - yes you know
Ill take your tests for comparison and advice as always.

@Bernd
I think I see in my head how you are doing this. I will muck about with it and holler if I have any questions.


Thanks Guys

Bryan

[dave_e]

HI, in ref to SlowDown's mention of TreeView/ListView, I am reminded that Keyless items are bound to load faster because there is no unique test required when adding items to the control's collection; the more items, the more tests for uniqueness, the longer things take. Not sure if this is relevant but hoping it's somehow helpful.
Best Regards
Dave

[gbison]

I am reminded that Keyless items are bound to load faster because there is no unique test required when adding items to the control's collection; the more items, the more tests for uniqueness, the longer things take.

Thanks Dave, I have actually seen this take place already while trying to load 20,000 files into a list view. It does get slower....