I'd recommend to find another teacher. He does not know what he is talking about.

First off all, as others have pointed out. VFP is a full object oriented language with inheritance, polymorphism and including constructors and destructors. Its important to point out that by a OO purity standpoint of view no existing language is purely OO. VFP has no native column and row objects (as ment) because it is handling data in a total different way, namely a relational way. Therefore VFP has more flexibility in ORM (Object Relational Mapping). OTOH, You can use ADO with oledo to mimic that to some extent. There definately are advantages and disadvantage to the way VFP is handling data. Overal VFP developpers would argue that handling local data is much easier in VFP compared to .NET.

This is just an example of the holy language wars, where people are using arguments from heresay without actually knowing the details. VFP is an older language that will not be enhanced in the future. I'd think that this in itself is a way more important fact, even though you should realise that each language comes and goes. OTOH, there still are COBOL programmers making an awfull lot of money (way more than the average .NET programmer).




>By the way, my teacher is teaching us vb.net
>he also says that vfp that does not have the concept of object column and object row while managing the data but .net does have those concepts, is true?
>
>One last question
>Why many professionals that work with .net and people that give speechs in the msdn communities talk bad things about vfp
>although is not true?
>Why ? a conspiration against vfp?