I aimed my comment a little far, bringing DDD to the conversation,
because DDD is a way to develop software that truly reflects the
business -the domain- using an object oriented approach.

Working with VFP or a RDBMS alone, we are unable to model and persist
objects that truly represent a domain entity ( a computer like the one I modeled above )
in a inventory system for example without a careful table design, that will be
hard to change or get rid off in case the business requirements demands it to.

To do so, we should be able to deal with that object, to know its model like we do
with table schemas.

We know XML & XML schemas are a pain to deal with; and Json & Json schema are
easy, lightweight counterparts, but still strange to Vfp, and no tools
or framework exist as a working solution.

Talking about VFP, It will be again a 1st class citizen in today's web-intensive development
environment, by not only being able, but a preferred way to, work with true objects that reflects in code,
right in front of our eyes, the ones we are dealing with in the real world.

That goes by using hybrid solutions ( noSql techniques using json fields ) so we can easily
extend, evolve , redesign and connect our systems in ways we never thought were possible.

( and it does not conflict anyhow with FIC ! )