BKtechie said: If anyone out there runs into problems migrating a dBase V app from Netware 4.11 to Netware 6, I have a tip. If you begin to experience index file corruption on large files routinely, check the setting "CLIENT FILE CACHING ENABLED". It should be set to OFF.
Okay, here's a second belated comment from me. We had Novell 5 using IPX and had data issues. Many tables were missing EOF() markers at the end of the DBFs. Sometimes the print job got written into a table. Sometimes it was a BROWSE screen. Occasionally a corrupted index that had to be rebuilt. As the network got busier it got worse. The server wouldn't go more than 45-60 days before it started "thrashing" with lots of disk access but little serving. And when a computer workstation messed up, would always do it again on all subsequent retries after the table was fixed. Only a reboot would return the workstation back to normal. Some stations were more prone to act up than others, but no predictable rhyme or reason why.
Apparently TCP/IP and IPX don't like each other, as mentioned above. Finally we switched to Win2000 server (making Mr. Softie happy, I'm sure) and the problem went away. It was a frustrating experience.
One final idea: If you use data compression on the server, sometimes a INDEX ON [expr] TAG [name] will fail! because the .MDX isn't actually decompressed and so the appending to the index causes an error. (A common setting for data decompression is to not decompress the file itself until there have been 2 accesses, so backup won't trigger all files to get decompressed.) Sometimes I would used the table twice or packed it first to force a decompress, then added the additional index.
