I have a program which checks a directory to see if a given .dbf file
exists.  If it does, then if checks to see if the companion .cdx file
exists.  If it doesn't, it generates the index quick.  Then, in either
event, it copies over the .dbf and .cdx files to a different
directory.
Now, I tried this on one computer, and it worked fine.  I tried it on
another where the files are being moved on a shared D: drive, and it
seems that the index only worked when it was already there - if the
procedure created it just before copying, the copy didn't work.  I am
using an SQL statement to make the index, and I do indeed close the
database immediately after.
My question is, are there any undocumented issues with file
manipulation in VB on shared drives?  I also noticed that FileCopy
wasn't working properly for a while, then suddenly it cleared itself
up -shrug-.  I've tried to change my db.close statements to set
db=nothing, but I don't think it helped.
Thanks!
MacK