jacksonmacd
Programmer
Not sure whether this is the right place to ask this question, but here goes:
Trying to put a filesearch object into my PPT97 application. As a test, I am searching for all files with a "7" in the name. Using the Search from Windows Explorer, I can search for files like: *7*.* in a folder, and find several files.
Yet when I repeat the search in the Advanced Search of FileOpen dialog from either Word or PPT, no files are returned. Similarly, the following code snippet returns no files:
Set objSearch = Application.FileSearch
With objSearch
.NewSearch
.PropertyTests.Add Name:="Filename", _
Condition:=msoConditionIncludes, _
Value:="7"
end with
How can I make the filesearch object return the same file list as does Windows Explorer?
Thx
BTW -- I find it ironic/typical/frustrating that the Help for FileSearch says that the Name property corresponds to the Value of the Property Box of the Advanced Search. However, the advanced search uses "file name", while FileSearch object uses "filename". Minor difference, but enough to cause a proram error. Dontcha just love MS consistency??
Trying to put a filesearch object into my PPT97 application. As a test, I am searching for all files with a "7" in the name. Using the Search from Windows Explorer, I can search for files like: *7*.* in a folder, and find several files.
Yet when I repeat the search in the Advanced Search of FileOpen dialog from either Word or PPT, no files are returned. Similarly, the following code snippet returns no files:
Set objSearch = Application.FileSearch
With objSearch
.NewSearch
.PropertyTests.Add Name:="Filename", _
Condition:=msoConditionIncludes, _
Value:="7"
end with
How can I make the filesearch object return the same file list as does Windows Explorer?
Thx
BTW -- I find it ironic/typical/frustrating that the Help for FileSearch says that the Name property corresponds to the Value of the Property Box of the Advanced Search. However, the advanced search uses "file name", while FileSearch object uses "filename". Minor difference, but enough to cause a proram error. Dontcha just love MS consistency??