[AccessD] FS object

VBA was fastest, API 2nd and FSO was, as you say, orders of magnitude 
slower.  I never did a thorough comparison of the FSO because not one of the 
5 locations at which I needed directory/file management tools had the 
scripting runtime enabled.



Ciao
Jürgen Welz
Edmonton, Alberta
jwelz at hotmail.com





>From: "Bobby Heid" <bheid at appdevgrp.com>
>
>I found quite the opposite using the dir function in VB6.  The API (not the
>FSO) was orders of magnitudes faster in getting all of the file names and
>information about the files off of a large hard drive.
>
>Bobby
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jürgen Welz
>Sent: Tuesday, May 04, 2004 10:34 PM
>To: accessd at databaseadvisors.com
>Subject: RE: [AccessD] FS object
>
>
>I find the scripting runtime is not enabled in many environments.  Hence no
>FSO.  VB(A) is incredibly fast in working with the file system.  File size,
>date modified and file/folder names are immediately available from the Dir
>function.  I ran a test comparing the API dir performance with VBA Dir and
>the VBA was faster.  The api could retrieve file creation time and
>additional attributes but at a cost of performance.  You can create
>directories in less time than it takes to load the FSO.
>
>I have never had to provide any file system functionality that wasn't
>already built into VBA.  When the job calls for a scalpel there is no need
>to get out a chain saw or a back hoe.  It's also like a comparison between 
>a
>
>public shared plastic spoon vs your own private silverware.
>
>Ciao
>Jürgen Welz
>Edmonton, Alberta
>jwelz at hotmail.com

_________________________________________________________________
STOP MORE SPAM with the MSN Premium and get 2 months FREE*    
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines