>>I only have one thought to add to this thread. This is, I always seem to be seeing in some way, shape or form, the abilities and advantages of VFP and FoxPro 2.x before that being undermined by, pardon the adjectives but, misinformed idiots. This thread can answer another threads question of why there seem to be more jobs for VB than VFP. If the DevDays agenda goes as suggested then VB will be seen as M$ developing cornerstone while VFP is just a third rate afterthought.
>
>There is more VB developers that VFP developers. That is because both products are focus for 2 different audiences. We can't compare both. They are dedicated for their own market. You have about 1/10th of today's application which required a powerful database and CLS front-end and full OOP engine - just to name a few big names. The rest is mostly small applications where VB can do the job and VFP might be overkill.
>
>As for a third rate, this is also related to big companies boycotting VFP. I've seen big companies throwing thousands and millions to the window because they have to remain in VB environment to develop big database application which requires also OOP. Yes, I mention OOP because for most of those companies, they thing VB is OOP. It is also related in part to the fact that VB is shown everywhere and IS people thing this is the bible. We also saw some evaluations from a big company, not the mention the name, where big companies are reading their evaluations as a bible as well. On the other end, as stated yesterday, VFP as survived without having marketing, at least, far from what VB had. But, this didn't help to have VFP recognized by many corporations where it is totally forbidden to use VFP to develop and where the requirements of some applications are to do develop in OOP and benefit of full powerful database and C/S engine. Yes, I always missed that part and always found that to be a
>joke.

I agree with you, but want to add one lighter thing: VFP is actively used by some biggest NYC corps, such as Chase and Citibank.