>Here is the solution I came up with and has worked ever since the last post.
>I have other tables which are fairly small with memo fields and none of them ever seemed to get the same kind of corruption as my notepad ones do. The notepad tables had one big table with a loan account field and 4 or 5 memo fields to each account number with an index on the loan account number to get to them when the application went to that certain account number.
>
>What I did was took the first four of our account number (which makes up a package for us) and made a folder called NP and in it I split up folders by the first four of the packages of the accounts. Within that I have each full 8 digit account number as a sub-folder. Within that I have an dbf and fpt for each account. No longer even a need for an index (cdx). I then use that table in the location based on the account I am in.
>
>This has worked without a single flaw since then. Anyone having issues with memos, I hope this helps.

Thanks for the follow-up.

Thomas was right to point out Novell 6. Casting my mind way back, there were some client-side settings that had to be configured for reliable operation for VFP apps. Some are still listed at http://fox.wikis.com/wc.dll?Wiki~NovellVFPIssues~WIN_COM_API . If I recall correctly the most important one was at the bottom, "SET CLIENT FILE CACHING ENABLED = OFF".

Sometimes what happens in legacy environments is PCs get replaced, client software for the legacy server(s) gets reinstalled but the critical client-tweaking step is missed. So, you end up with new machines on the network with unreliable client settings.