>>Craig, my friend, I hate to say this, but both you and Ryan are "offBase" here.:-) Whether we like it or not the language (which is what ther term was referring to) is xBase. Neither you, nor I, nor Ryan, nor Microsoft can change that without completely getting rid of the product as we know it. It can be a positive as well as a negative. You can market it towards those who use other xBase products.
>>
>>While Microsoft has attempted to change the perception of VB, it remains that BASIC is still an acronym, and the B stands for Beginner's. You don't hear VBer's complaining about that.
>
>
>I'm not arguing the fact that VFP is truely an xBase language. I'm saying, let's not market it that way. As I said, xBase has a meaning of old, obsolete, outdated. If we continue to market VFP as an xBase product, it will only appeal to xBase developers, and we will continue to see it's market share erode, thus causing the long discussed death of FoxPro to become a reality.

Let's market it as RAD/OOP tool which is backward compatible with xBase... :)