>>I've heard a lot of talk both here and at the LA Fox Group, you know, the doom and gloomers. But I would have to say I agree with Jim Nelson in respect that M$ has run a compaign against VFP. If Microsoft had given the product the exposure it needed we probably would be at 2,000,000 instead of 500,000... maybe more. Lets hope that its not for some trivial reason like they don't like the name "Foxpro". But the real question is why are we still here? Is it really worth keeping a software for 500,000 cranky, belligerent, fanatical, pessimists? ( As we have been labeled. )
>>
>>Just curious.
>
>I'm not even going to try to respond to this one. I'm just gonna sit back and watch the flames fly.

Okay, I'll go first. If ther is one thing I have leaned in 30+ years as a programmer it's don't get too attached to a development tool. It's the nature of the business... and we are at least partly responsible. We always want bigger, better , faster, and smarter with less and less input from the developer. I, for one, am not interested in returning to COBOL B or AUTOCODER or the always popular Z-80 chip.

Don't get me wrong. VFP is beyond any doubt my tool of choice. On the other hand, if SQL Server better serves my needs, that is what I will use. If, for some reason, you need an incredibly stupid GUI interface then VB is the obvious choice. A program that is calculation intensive may be better in C++. My point is, like it or not, VFP is not the be all do all tool we might want it to be.

Things change. Stuff happens. Get over it. Make full use of every resource available to you to produce the best results possible. Use and support VFP whenever and wherever possible. And most of all be ready for changes because they are lurking just around the corner. VFP isn't going away but it may get harder to recognize.

Hope to see you at DEVCON 2025.

Bob