James,

I *am* relaxed....so relaxed on a Friday aft that my client is probably going to start asking questions. I am a die-hard FoxPro-er having been with the product since FoxBase days (ca. 1987). The only way that I will ever switch is if a) MSFT kills it (not likely, IMHO) or if my clients tell me to use something else and the moolah dries up. Fortunately, I work for smaller (but well off) clients who don't give a diddly what it is written in as long as it works.

But hey, I might have said something intelligent here - maybe we *can* make some bucks off of teaching VB guys OOPS - while we are at it though, we don't denigrate either product...we just teach it and ever now and then, if VFP has a better implementation of a feature, let it be known.

Albert

>Albert,
>
>Relax. VFP is not going away that quickly. And VB will eventually grow up to be a fully object-oriented language. There will be some shake out. Alot of VB hacks will leave the fold, and a lot of VFP developers will learn VB. Bottom line is, don't sweat it! There will be a place for both products, and neither product is going to swallow up the other one like PAC MAN.
>
>The point I was trying to make earlier is that it is useless to cry over VFP's lack of respect in the IT community. This topic has been beat to death. What we need is a positive shift towards embracing a future with new technologies, VFP included!