>>>However, what happens if you go three tier? I think inheritance in VFP will kick VBs butt here.
>
>OK...
>
>How often do you take advantage of multiple layers of inheritance with COM components? How about events, which is at the core of multi-tier architecture?? How does inheritnace address that? It does'nt.

I go three layers deep. In VB I have to write an error handler in every object. Dumb, dumber, dumbest. Write it once and have it inherited. My top level class is is based on the VFP Session class. Then I have a bizRules, then a DataRules class. Everything else is based on those two. The error handler is defined in the top level class.

As for events, I don't have a problem not raising them. The only thing I really need to worry about are errors and they are handled quite nicely with COMRETURNERROR(). It might make some routines easier to code if I could raise events, but I'm ok with the way things are now. Your experience may indicate differently as I'm sure you've developed more and larger multi-tier applications that I have. But for what I've done, VFP handles it fine.

>
>Look ,I am not saying that VFP does not have advantages, it does. But, to make a general statement that VFP kicks VB's butt because of inheritance is a bit misleading. In reality, regarding which tool to use, it really depends on a multiude of variables..

VFP kicking VB's butt in the middle tier due to inheritance is my opinion. If you want to think differently, I have no problem with that. Inheritance isn't the only reason. Munching on the data in someway is another.