>>>Inertestingly enough, I had this problem on a straight '98 peer to peer network. No novell at all. It happened when I did an append from, or when I packed a table across the net. I am running noname P2/266's. Two byte shift, chr(0) shows up in the first field of the table for a few rows, then goes back to normal.
>>
>>Todd,
>>
>>I'd blame it on the underlying networking OS before I'd blame it on VFP (or FPW for that matter). That's what controls the file I/O, not FoxPro.
>
>Ah, but this is just the thing I'm looking for! Here we have an instance of the "corruption" problem w/o Novell being involved at all. However, we have the common thread of PII processor and Win98 which I also have.
>
>Todd, do you recall if the workstations were using PCI network interface cards as well and what manufacturer? Were they 10mbit or 100mbit cards - or were they autosensing - 10/100? Also, was this with VFP, FPW, or FPD? Also is interesting that it is a null character being inserted. Novell told us that they have another ticket open with another Novell customer using a Dell PowerEdge 2300 and a Cobol application. This customer has reported that null characters are being inserted into the file. I'm really beginning to suspect an O/S - hardware problem here rather than just a client since I'm discovering more and more people having this problem who are not running the client.
>
>Thanks for everyone's responses - I think I'm going to set up a "test" peer to peer network and see if I can reproduce the problem by using different combinations of hardware.
>
>Thanks,
>
>Joe Miller
>jmill@ezo.net


You may be onto something there with the PII's and W98. It was only the new workstations that were this combination that seemed to be having the problem. I'm not sure what the Compaq's that replaced the funky workstations were, but they may have been the AMD processors, not PII's.