>>As far as OOP goes, when it comes to middle-tier development, VB and VFP are >essentially the same level. Why? Because inhertiance plays little or no role >in middle-tier work. As far as a flexible cursor engine goes, yes, that is an >advantage of VFP. However, I don't think you can really demo that in 15 minutes.
>
>I don't think so. In VFP you can create a custom business object class that has standard methods defined and standard behavior defined in those methods. In VB, you have to create this for each business object. I think not having to hand code each Insert, Update, Delete, retrieval of a list of records, etc. is a pretty big advantage that you get from OOP. But, could you do this in VB by creating a base business object in a DLL that handled this kind of thing?

I assume you could create a persistence class that is reponsible for saving busines objects, and you could use this class when you needed to save your business object... basically taking all the common functionality out of the BizObj into a seperate class, and using that class in each bizobj instead of subclassing it...

This is actually a technique (behavior classes) that you can use in VFP to have a cleaner class hierarchy. It is basically the Visitor pattern I believe.

BOb