>Honestly is not bad idea at all :)
>Especially that table pointer field alowing it to span into
>multiple memo containing tables.
>
>I did something simillar back in Clipper days due to memo bloat/corruption
>problem, but instead of saving it as actual memo, I sucked out all
>actual memo lines and save them to another table as fixed lenghth
>character fields. Reversible process wld later reconstruct entire
>memo/text for subsequent editing.
>
>Now days with OOP / session objects I wld build actually separate session (tear) object in charge of doing that and simply send / request memo back and fourth. But I did not came across such need just yet.
>
>I managed to avoid 2 gig limit by building usualy yearly databases for my
>mostly financial / general bussiness apps and believe it or not, ever since I moved to VFP, I almost forgot all about memo/table corruption :)

Thanks for the feedback