>>>>>What is your position on using stored procedures? They are encapsulated in a single location.
>>>>Again. Encapsulation is a feature of the design of objects, not an aspect of how the source code is stored.
>>>
>>>For objects, perhaps. But encapsulation exists beyond objects ... into source files, for example.
>>
>>No. Look. If I take a blueprint of a building an put it in a drawer, does that mean the building is more encapsulated? All of programming is about the execution of the file at runtime. If you give me one file or 8 separate files, that is not more encapsulated because it's not important to the operation of the code at runtime.
>
>FWIW, I'm astounded beyond belief you are making this argument. I disagree with your thinking 100%, and we'll never agree on this.
>
>Keep coding as you're doing. VFP can work with your model, and my model. It's highly adaptive and flexible.

Unfortunately, that very kind of obtuseness is what leads to such differences. It causes products to maintain backward compatibility. You only show you don't understand the computing specific use of the term encapsulation. The code is encapsulated into an exe. Any other aggregation is human-induced and reduces performance.