>>>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)?!
>
>There's a Windows setting (not sure whethere it's local or on the server) that controls whether persistent drive mappings are retained full-time. IOW, mappings may connect only when accessed and may time out.
>
>Sounds like you're hitting a timeout.

UPDATE: Well, it turned to be a sequence of three bugs (one of which I encountered yesterday after getting your post that I won't even try to go into now<g>).

I believe that the problem was data corruption after all. When I had originally tried to fix this by copying the tables over to a new location, that's when I encountered the second bug which, as it turned out, only occurs when executed on the TS box I was dialed into. Apparently, some weirdness in Win 2k SP2 and TS, I suppose.

Copying the tables over from another work station and recreating the indexes appears (at this point) to have solved problem. Thanks for the help, Dan!

Later...
/< /-/