>SAVE TO FileName | MEMO MemoFieldName [ALL LIKE Skeleton | ALL EXCEPT Skeleton]
>
>which gave you "document data store" looong before XML, REST or JSON were invented.
>
>And going via memo field was exceptionally fast on very early nineties HW - IIRC I blew away competition with IDE drive and 80486 on DOS FP with that specific trick to emulate something we now call "table buffered input": Ability to edit several records and then deciding to save or throw away was unheard of back then - I fell in love with the idea after reading a book on FP-Dos capabilities which included an array-based approach to refrain from binding to .dbf records directly.
>I "iust" ran with the concept ballooning it into enabling buffering inside a single table, as work areas were not abundant like today...

Ditto... in a different way, of course. I stored a whole array, plus a bunch of other variables with the same prefix, into a memo and then later used that as pretty much config. Sure, the variables were private when restored, but it still worked like a charm. In other cases, in a dental app (FPD2.6), stored the whole jaw in a couple of 32-row arrays, and that was patient's dental record.