>Have you worked with the Implements keyword? Multi-casting? Delegation design?
Composition?

Nope. I have an idea only but not clear yet. Thanks for giving me an assignment. :)

>(I would also argue that inheritance is used too much by most VFP and Java programmers, and even in those languages the careful use of delegation/composition would create better, less memory-intensive, and more extensible apps. But that's for another board.)

Sounds like John Petersen's stand on inheritance abuse eh. When to say that inheritance is being used too much?

>Imagine how you would feel if a VB programmer looked at VFP and said "you can't Implement? Or god, you can't reuse code in this stupid language! Oh well, maybe in VFP 7..." and began cutting and pasting and posting comments that this was the only way to work in VFP. He'd sound pretty silly, wouldn't he?

I don't have problems with re-using Functions that gives or produces the same output in VB. What's lacking so far is subclassing a form or object in order to avoid cutting and pasting. Just imagine if you have 100 forms that uses similar properties and methods without inheritance. How do you accomplish this in VB?

100 forms which have the same properties and methods:

Private Var1 As String
Private Var2 As Boolean
Private Var3 As Integer

Public Delete_Record()
End Sub

Public Add_Record()
End Sub

Do I have to create a form which will serve as template form and then start the code from there? How about the maintenance issue?