I couldn’t agree with you more. Our framework is designed with multiple executables and ALL objects are instantiated with NewObject(). The problem in VFP 6.0 using NewObject() is the class being instantiated in the other executable has to be based on a VFP base class or the parent class must be in the same program as the class. The later of the two methods breaks the ability to maintain a parent class in one location and the first does defeats the purpose of OOP all together. It seamed a bit backwards to have to issue SET PROCEDURE in one executable in order to instantiate a class in another executable. This little enhancement makes it possible on build true component-based applications.
