>>I kinda thought about the disk quota thing, too. But, the network admin swears up-n-down that there are no disk quotas.
>
>Don't they always? <g> I've had Novell CNE's SWEAR up and down that the owner of a directory hasn't been deleted, until they go look when I'm looking over their shoulder.
<bg> I'll remember this. The bad thing here is that I'm using TS (terminal services) and I can't look over his shoulder.

>>From an Explorer window I can cut-n-paste the entire directory tree. I just can't copy a big file (>20 MB, in this case) from a command window and this includes any of the other data directories.
>>
>
>Hmmm ... can you COPY FILE from within VFP?
Yes, I can COPY FILE. Also, the network drive where I'm trying to COPY TO is actually a drive on the local machine. If I go to the local drive instead of the drive mapping, I can execute the COPY TO successfully.

I just noticed that if I open up a "My Computer" window with the list of local and network drives, try to COPY TO until I get the error, and then glance back at the "My Computer" window, the network drive has a red-X on it. If I single-click on the network drive, it reconnects. So, it appears to be disconnecting for some reason (just like the VFP message indicates)?!

>>However, the main problem is the "C" errors but they sound related to me. What do you think?
>
>Definitely sound related.
>
>>Oh yeah, this is a Windows 2000 network. All of the boxes are newer P4 Compaq boxes and the server has a SCSI Raid array.
>
>Ooooh! One of the drives in that RAID array could be marginally flaky. Fox will find it when that happens. It's the great breaker when it comes to hardware. If there's one loose chip that needs wiggled, Fox will find it. Flaky drive? Fox will find it with surgical precision and won't know how to deal with it so it throws a C5 error.
>
>RAID is supposed to avoid this kind of flaky behavior, but that hasn't been my experience.
As I mentioned up above, I can successfully COPY TO if I run it on the local drive versus the network mapping to the same local drive. Me thinks something is definitely "wunky" with the network.

Later...
/< /-/