>Let me ask you this: How many langiages do you program mwith? I currently use VFP for about 85-90% of my work and SQL scripting is going to take a larger future percentage as well as VB6.0 for the simple reason that VB makes easier to implement COM objects from everything I can discern, even though I plan to use VFP for all of mine until forced to do otherwise.
>

The payout for investment in learning the VB language is dramatic, too. In addition to writing native VB applications, what you learn is directly applicable to things like VBA, VBScript and similar tools. I see the benefits of a common language for controlling things; one thing that made WSH very attractive to me beyond just the automation objects available inside of VFP was the availability of a 'real' scripting language for replacing things like .BAT files with a more powerful tool, without having to drag along Perl or Rexx and try to integrate them as well. The Javoid among us might find JScript more pleasing, but it doesn't pay the dividends for the Wintel platform that a knowledge of VB and VBScript pays.