Patrick

Tushar – I don’t like relying too heavily on sheet names or specific cell values. Users change things like this. I use the sheet code name if I can predefine it (i.e., the sheet isn’t added on the fly), or hidden names at the workbook and worksheet level. I use custom properties to store the version number or date of files, so I can read them in Windows Explorer, and I have dsofile.dll on my dev machine so I can set them on closed files (and on non-Office files, like PDFs).

(1) I did not use FileSearch until recently because some folks (I don’t recall who) had reported that it did not find all files that met the specified criteria.

(2) I suspect there is some Windows API (or combination of APIs) that will give you what you want. For example, with FileSystemObject I cannot find any information about an image but Windows Explorer reports on things like size, resolution, bit depth, etc. So, there must be a way to get that information

(3) For reasons now lost in the haze of history, I had considered and rejected the use of custom properties to identify files. One reason might be that I wanted a way to check not just the active workbook but also the activesheet. Currently, I rely on one of two techniques: either the name of the worksheet has to be so-and-so or a predefined cell must have a specific ‘tag’ value.