>Hi Craig,
>
>I would like to engage you in a discussion/debate here...

Uhh..OK...but given your C/S experience, I have no doubt you'd win.

>
>If the issue is connectivity to SQL-Server, which is probably a requirement, how does inheritance play a role in the decision making? If the question relates to comparing VB and VFP on the basis of creating UI's or components, I can see how inheritance is a factor. However, for data connectivity, I don't see it.

For connectivity via ODBC, it doesn't really matter. VB or VFP will work. However, what happens if you go three tier? I think inheritance in VFP will kick VBs butt here.

>
>IMHO, you have neglected to expound on how ADO/OLE-DB is better integrated into VB. The fact that VB natively supports COM events, which is important for asyncronous processing.

Is there something there that you can do in VB that can't be done in VFP using the VFPCOM.DLL and binding to ADO events?

>
>Sorry, I don't see tossing VB aside just because it does not support inheritance. At the very least, it does nothing to address the question at hand.

I agree, inheritance alone is not sufficient reason to toss out VB.

>
>