>>I personally chose VFP because our main accounting application is SBT 5.0, which is written in VFP5.0. We bought the source-code for it because our businesses are so diverse (everything from funeral homes to plastics manufacturing) and now we can "stretch" the software to cover everything in one package. I'm actually more into C/C++ (you can call me "Poseidon, God of the C" ).
>>
>>Did you hear that the new version of VB will finally support inheritance? The snippet I read stated that they went and "borrowed" all the inheritance technology behind VFP and added it into VB 6.0 - so now it should be truly Object-Oriented instead of just "Object-Based".
>
>It will take more than inheritance in VB to make it full OOP ready.
>
>As for borrowing technology from Visual FoxPro, I, most of the times, consider it as a good sign. That is a good way to show the power of the Visual FoxPro engine. We've seen that before when MS included some of Rushmore technology in Access. Could SQL Server be Rushmore optimizable? ;)

Michael,
What he is quoting on VB getting inheritence from VFP is a scam!! It is from an April 1st article ment as a joke!!

VB would require a major rewrite (as posted by Jim Booth in a few places) to have the OOP model that VFP does...