Hello:


Glad to find a place to ask question in regards to VB6. Here it is. I have a
search routine in VB6 that worked great on XP -

Set fs=Application.FileSearch

but when I updated to Vista, it is giving me a Run Time Error Code 445.

Any thougts and or suggestions to get around this besides going back to XP
or up to VB.Net would be greatly appreciated.


Thanks,


10_a_c

10_a_c wrote:
> Glad to find a place to ask question in regards to VB6. Here it is. I have a
> search routine in VB6 that worked great on XP -
>
> Set fs=Application.FileSearch

That doesn't look like VB6 to me. I think we need more details here. (Is this that
abominable FSO thing, by chance?)

> but when I updated to Vista, it is giving me a Run Time Error Code 445.

What's the Err.Description at that point?

> Any thougts and or suggestions to get around this besides going back to XP
> or up to VB.Net would be greatly appreciated.

Upgrading to XP is always a preferred route when Vista is involved. <g>

And, around here, you won't find anyone who thinks VB.NET is anything but f'd up!

More details will help. This is likely quite solvable.

I think some of the Office apps have an Application.FileSearch. Maybe it's
not VB6 but VBA?


Rob

Karl E. Peterson wrote:
[..]

Robert Morley wrote:
>I think some of the Office apps have an Application.FileSearch. Maybe it's
> not VB6 but VBA?

You're probably right. Yeah, looks like it's part of the Office Object Model...

http://msdn2.microsoft.com/en-us/lib...ffice.10).aspx

I think the OP needs to provide a little more context/code to have any hope of
troubleshooting, here. None of the examples on that page show the sort of usage he
suggests.

Hmmmm, a little googling makes me think perhaps we're not getting all the
information!

http://www.mrexcel.com/forum/archive.../t-250502.html

Turns out FileSearch was *dropped* from Office 2007. So much for "COM is a
contract!", huh?

On Thu, 14 Feb 2008 17:37:54 -0800, "Karl E. Peterson" <karl>
wrote:
in <eSVejN3bIHA.4144>

>Robert Morley wrote:
>
>You're probably right. Yeah, looks like it's part of the Office Object Model...
>
>[..]
>
>I think the OP needs to provide a little more context/code to have any hope of
>troubleshooting, here. None of the examples on that page show the sort of usage he
>suggests.
>
>Hmmmm, a little googling makes me think perhaps we're not getting all the
>information!
>
>[..]
>
>Turns out FileSearch was *dropped* from Office 2007. So much for "COM is a
>contract!", huh?

Thought you'd be amused with this:

http://www.techyouruniverse.com/tech...-for-microsoft

Hmmm...interesting. I wasn't aware that they'd dropped it. Oh well, it was
at least as clunky as FSO (probably based on the same thing) and buggy to
boot as I remember it from the one time I played with it many years ago.


Rob

Karl E. Peterson wrote:
[..]

Stefan Berglund wrote:
>>Turns out FileSearch was *dropped* from Office 2007. So much for "COM is a
>>contract!", huh?
>
> Thought you'd be amused with this:
>
> [..]

HA!

Key reason #1 - Microsoft is anti open-source, Yahoo! utilizes open source
technologies extensively.

Key reason #2 - Microsoft is evil, Yahoo! is not.

Key reason #3 - Microsoft technologies suck.

That's great. :-)

Robert Morley wrote:
> Hmmm...interesting. I wasn't aware that they'd dropped it. Oh well, it was
> at least as clunky as FSO (probably based on the same thing) and buggy to
> boot as I remember it from the one time I played with it many years ago.

I'm sure it was too fragile to support. Anything filesystem based is, in an object
model. <g>

Nice...except for the bit about the Mac OS being better than Windows. I'll
admit it's been several years, but every time I've looked at any variation
of the Mac OS, I've absolutely hated how dumbed-down it is.


Rob

Stefan Berglund wrote:
[..]

Robert Morley wrote:

> Nice...except for the bit about the Mac OS being better than Windows.
> I'll admit it's been several years, but every time I've looked at any
> variation of the Mac OS, I've absolutely hated how dumbed-down it is.
>

Ironically, MS, with their infinite capacity for self-doubt and competitor envy,
seems bent on doing their best to dummy-down Windows as far as possible. "If we
aren't worse yet, wait till you see our next version!"

Thanks for all the response and assistance. It is VB6 and this routine
searches the computer for particular file names -

Sub AdvancedFileSearch()
'
List1.Clear
Screen.MousePointer = vbHourglass
Label1(6).Caption = "Searching for files; please wait."
Picture2.Visible = True
Set fs = Application.FileSearch ' searches for excel files
For startnumber = 1 To 2
With fs
.lookin = Drive1.Drive
.SearchSubFolders = True
Next startnumber
' ...
End Sub

This program does interact with Excel to post results of the search of
various Work Orders. Is there a workaround?


Thanks,


10_a_c

"Karl E. Peterson" wrote:
[..]

Hahaha...you've got a point there!

Steve Gerrard wrote:
[..]

If it IS VB6, then you'd have to find out what the Application object is, as
there's no Application object in VB6, and the App object (which is similar)
has no FileSearch method.

I'm reasonably sure that would be an Excel.Application object, which does
indeed have a FileSearch in versions prior to 2007. Check which version of
Excel is installed on the machines where your code is failing. If it's not
2007, then post the code that defines what the Application object is so we
can help you further.


Rob

10_a_c wrote:
[..]

Hello Rob:


Well after further review, you are correct in that it is not VB6 but Office.
I think that other people suggested that it might be and noted that Office
2007 no longer supports FileSearch.

Anyway, my program searches a selectable drive and finds certain excel
files. It then opens each file serparately in Excel and extracts info from
each based on certain criteria. Others have suggested FSO and I am looking
into that one.

Any thoughts would be appreciated.

Thanks,


10_a_c

"Robert Morley" wrote:
[..]

FSO is generally NOT recommended, as it's very slow and consumes a lot of
memory. It's also disabled on some systems, particularly those that have
been locked down by corporate IT departments and the like.

That said, if you're coming from the FileSearch functionality, you may find
it easier to use.

Typically, the functions built into VB (either VB6 or VBA) are enough to do
the job, but they're fairly low-level, so if you're trying to do something
like a recursive search, you'd have to write the code yourself.

For added fun, there's also a design flaw with the Dir() command, where it
keeps a lock on the last folder you used it for until you read past the end
of the directory. If you decide to go with the lower-level commands, you'll
need to either code around that (usually not a big problem in a recursive
search), or use API calls, which don't have that bug.


Rob

10_a_c wrote:
[..]