>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.
>
>Kev

Hi Kevin:

Since the last time I answered, I've found new info that may be useful to your case.

Disabling SMB2/3 may have bad secondary effects. I've read that the only thing that needs to be configured are the clients.

Look at this:

http://www.pcwizardsinc.com/home/visualfoxprosqlerror2066corruptedindexes

Regards.-