>I was using DOS commands in NT (NET USE, etc) and redirecting a DIR listing to a text file, then parsing that for each resource I needed a listing for. (ADIR has never been able to get it done like I needed it.) However, I started using the API to map to each drive (I have to connect to 28 different users and get a file list) and I am looking for a faster way of getting the DIR listing. Redirecting the DIR command to a file, then adding that txt file to a table then parsing it to weed out unneeded info has been working fine, just taking too long. (Each user is a design engineer with literally thousands of CAD drawings I have to mill thru.)
>
>So far I've been able to improve speed a little using WSH and pouring the results of what I'm doing into a table, but I really wish ADIR() worked as advertised. (I've NEVER been able to get info contained more than one subfolder deep, even when using the D switch with ADIR().)

Well, I don't use adir. I send the redirected output to a text file ,then create a cursor and append. Then I create a second cursor and insert the information there. It allows me to run a select and pull out files based on filesize, date, subdirectory, etc. and it seems to be very fast.