Hi Rod,

Thanks for the idea. I will add this test to my code.

Now, what do I do if file() returns False? I know that the file exists (if this file disappears, my client's business pretty much goes to hell with it).

Obviously, when I re-run the program after the error, something is cleared-up/reset somewhere, for the file gets copied without a hitch. This, obviously doesn't happen during the three attempts that my code makes at copying the file.

Any ideas of what might be changing from one instantiation of my program to the next?

Thanks!

Alex


>Try this code and see what happens. this is from the VFP toolkit
>
> Public Shared Function File(ByVal cFileName As String) As Boolean
> Return System.IO.File.Exists(cFileName)
> End Function
>
>If this doesnt work look into a security issue with the CLR and accessing data on a shared drive.
>
>Rodman