>What I really mean is, why did vfp become more OOP than vb? Even if vfp isn't really going to die, it certainly seems like vb got 10 times the attention from Microsoft. Given that fact, how did vfp end up with more OOP features?

Perhaps 'tis because VFP is a developer's language and VB was not designed as such? Therefore, by making it object BASED, the 'everyday' user doesn't have to learn how to deal with things like sub-classing, inheretance , etc.

Just a guess........prolly the reason is "because it was cheaper"

"You don't manage people. You manage things - people you lead" Adm. Grace Hopper
Pflugerville, between a Rock and a Weird Place