>>The above program worked until it got to a file that was 24 MB. It counted up the records, gave the message that the records were copied, hung up for a while, and then came back with a "Error writing to file" message. At this point I'm also unable to browse the open table. I get an "Error reading file" message. Display status confirms that VFP thinks the file is still open. If I re-USE the file, I can then browse it.
>>
>>This sounds like some kind of weird network error. The client's network is running TCP/IP. Does VFP 6/7 run fine with TCP/IP? Is NetBios required for VFP? Any other suggestions? TIA.
>
>That *almost* sounds like a network diskspace quota was reached on the copy. VFP isn't graceful about such things.
>
>VFP is fine on a TCP/IP-only network -- if it's set up propoerly. <g>
>
>What's the Network OS?

>"Error writing to file" is usually VFP asking the network to do something, the network saying "no", and VFP giving the only error message that makes any sense to it.
>
>How ya been, by the way?

Well, I'll be! You didn't fall off the face of the Earth, did you?! Life's been grand up until this point. I'll PM you, later.

I kinda thought about the disk quota thing, too. But, the network admin swears up-n-down that there are no disk quotas. 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.

However, the main problem is the "C" errors but they sound related to me. What do you think? And like always, they're in a crunch to get a ton of data keyed in.

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.

Later...
/< /-/