>Kevin,this is the area where i am unable to grasp the concept of business obj in its entirety. >
Many developers have a tough time with this concept initially as with any OOP abstraction. It's hard to make the mental leap between a real-world object such as an Invoice to a VFP Class that represents the characteristics and functionality of an Invoice. I recommend Savannah Brentnall's "Object Orientation in Visual FoxPro" (Addison Wesley - ISBN 0-201-47943-5) for developers who are climbing the VFP OOP learning curve. It really helps solidify many of these concepts.
I've discussed this with Alan Griver and he agrees that in hindsight they would have done this differently and separated the user interface controls from the business object. They did it this way because it was a small app and there were places that they reused both the business object and the associated user interface controls.
Binding user interface controls to a business object isn't necessarily "wrong"...it's just not the best way to code an OOP application. For details on this concept, check out Jefferey Donnici's article "Separating Interface from Implementation" in the 2/97 issue of FoxPro Advisor.
>Also, the MMdoc says if reqd to drop a pageframe control on the Business object.( Building on the Quick start proj - step 4]. I am not very clear on this area. Would i need to modify any of the classes to handle pageframes ? Or will the CB3 modified as per MMdoc Ver 2 take care of this automatically ?
Oops! This is a paragraph that I should have taken out long ago. When using the original VFP3 Codebook's old style business objects, this was the suggested method. However, with the newly enhanced business objects, this is no longer true...and as I stated previously, I don't recommend binding user interface controls to the business object; just drop the business object on the form and then drop the associated user interface controls on the form.
Regards,
Kevin McNeish
www.oakleafsd.com
Kevin McNeish
Eight-Time .NET MVP
VFP and iOS Author, Speaker & Trainer
Oak Leaf Enterprises, Inc.
Chief Architect, MM Framework
http://www.oakleafsd.com
