>>>I think embolded is unproven except for functions still on the stack.
>
>The most accessible VFP hack involves reading memory to save the whole unprotected app that's easily converted back to the full project. IME this is reliable on a modern machine with heaps of resources, though (as you note) there must be some formula relating to % memory since Defox apparently uses it to help prevent this hack. Otherwise with "only" 256mb I'd expect there's enough capacity for almost any VFP effort...

Ahem, not mb, Kilobyte! From vfp9 help:

nBuffMemSize
Specifies the maximum buffer memory size in bytes. If you specify a value for nBuffMemSize that is less than 256K bytes, Visual FoxPro sets the buffer memory size to 256K bytes.

Specify 0 for nBuffMemSize to return the buffer memory size to the Visual FoxPro startup value. The startup value depends on the amount of your computer's memory. If you omit nBuffMemSize, SYS(3050) returns the buffer memory size for the buffer specified with nType.