>> Now that VFP supports multithreaded COM objects, the framework's use of business objects is uniquely positioned to take full advantage of this new functionality.
>
>Hi James,
>I'm also a big fan of the framework, but I'm curious as to your reasoning behind the above statement. Can you explain?

Separating the business logic from the interface and data source is what business objects are all about. A true business object should exist as an entity unto itself, independant of the data source or application front-end. Codebook business objects approach this philosophy, but could not be implemented because they could not be compiled into multithreaded COM components. Therefore, the business objects remained application dependant.

Visual Studio Service Pack 3 fixes this problem, and you can expect to see major changes in the framework in regards to how to build applications and designing business objects. I am very excited about the possibilities!

This new functionality lives up to Microsoft's promise of positioning VFP as the perfect middle-tier component in n-tier client/server development because of VFP's superior data handling capabilites and blinding speed.