Re: Invalid procedure call or argument - Dir function
- From: erewhon@xxxxxxxxxx (J French)
- Date: Thu, 18 Jan 2007 13:11:32 GMT
On Wed, 17 Jan 2007 15:50:43 -0800, "Karl E. Peterson" <karl@xxxxxxxx>
wrote:
guy_jara@xxxxxxxxx wrote:
Takeaway: It would appear that long periods of time between calls to
the Dir function causes it to loose "reference," if you will, to the
previously initialized search pattern, and moreover, to the function
itself.
That's an incredibly interesting observation! One that could be tested,
empirically, were one wanting to. It infers that VB is calling FindClose after some
set period of elapsed time. Hmmmmm....
Actually it 'implies' - sorry for being a nit picker
- I once got it in the neck, and try to prevent others getting tripped
up
( Another Delphi version of ForceFore posted today :-} )
My gut instinct hinges on the word WAN
The acid test would be using FindFirstFile, I suspect that Dir() is a
very thin wrapper.
The OP has done the smart thing
Pre-preparing data is the way to go
- and avoiding Dir outside tight (small) loops helps one stay sane
.
- Follow-Ups:
- Re: Invalid procedure call or argument - Dir function
- From: Karl E. Peterson
- Re: Invalid procedure call or argument - Dir function
- References:
- Invalid procedure call or argument - Dir function
- From: guy_jara
- Re: Invalid procedure call or argument - Dir function
- From: Karl E. Peterson
- Invalid procedure call or argument - Dir function
- Prev by Date: Like operator and square brackets
- Next by Date: Re: VB 6 Support
- Previous by thread: Re: Invalid procedure call or argument - Dir function
- Next by thread: Re: Invalid procedure call or argument - Dir function
- Index(es):
Relevant Pages
|
