>Hi,
><snip>But, is that the only solution?
>
>To be able to give a proper answer, can you expand on what is being stored in the memo fields.
>
>If you have to use memos I DEFINITELY would move to MSSQL as the VFP memo WILL break at some stage, and in some cases they are unrecoverable, with restoration of a backup the only alternative.

I remember this happenen to me nearly 20 years ago, just before my HD broke down completely. Actually, this is not a problem anymore, unless you have some bad connections or some other hardware problems. I have an application which is installed at about 4000 different locations, and we have never had any problems whatsoever with memo files. But yes, we ask our customers to run a maintainance program once per year, this program also packs the memo files.

>>>The limit is 2GB for each individual file. i.e. you have a fair way to go before you hit the limits.
>>>As far as adjustments, upsize to SQL.
>>
>>Well, the memo file is growing faster. It is true than that I am saving 100 Meg as the DBF is on another file. I have the infrastructure in place to move one table, if necessary, to SQL Server. In this case, that could be a justification. But, is that the only solution?