This one will go directly to my favorite folder :-)

Thank for sharing your optimism!



>Logical thinking and well said.
>
>To All:
>I've read so many "VFP is dead or terminally ill" threads/posts over the years that I've become accustom to just smiling most of the time and not deigning to post a reply. OK, so MS worked their tails off to create and release VFP 9 (the best release ever, hands down) and then a couple months later they're going to announce that VFP is dead and have a nice day? Thinking like that is irrational and born of fear.
>
>It's all good news and more good news... Ken has made it quite clear that VFP will be moving forward and that a Service Pack will be available probably by year's end. As to the next version of VFP, I don't care if they want to call it a non-traditional upgrade, a module, a package, or a chicken salad sandwich... an enhancement is an enhancement and is a good thing for VFP. Ken has also made it quite clear that VFP will not be integrated into Visual Studio .NET. This is a good thing, a really good thing, as integration would mean the same as it always has, giving up the stuff that makes VFP a worthwhile tool. When I'm working on a .NET project I use Visual Studio .NET, I don't, nor would I want to, use VFP. Ken has also hinted that we will be able to leverage Avalon for our user interfaces in the future... that's AWESOME news! Talk about being able to present data to the user in a way that will blow their socks off! They're planning on enhancing the reporting features further
>(VFP already the best built-in reporting features of any tool MS offers and it's going to get even better?)... again good news. "Extensibility, Extensibility, Extensibility..." appears to be the current mantra for the MS VFP Team and I'll gladly chant it along with them. They already working on many of the improvements/enhancements, so why on earth would they announce that VFP has reached its end? That's simply not accurate, reading between the lines or no reading between the lines.
>
>You know, years ago many of us watched as VFP app after VFP app was converted to VB and VFP programmers flocked to VB in droves because it was a foregone conclusion to many that VFP was dead. VFP would only be around for a couple more years at best. Now, here we sit... VB is DEAD and those poor converted VB apps will either stay as they are or are once again being converted because the language they were written in is gone. The story sounds a little familiar doesn't it?
>
>It should be noted that VFP is not only improved and made more useful by the MS VFP Team, but by the the VFP community. Serious about doing something to help? Write some useful VFP classes and functions and place them in the public domain. A quick look in the XSource folder and one can easily see that VFP can be enhanced greatly with VFP classes, prgs and Apps. Creating Articles and FAQs is also a good way to pitch in and ultimately improves the overall VFP experience as well as it's exposure. Join a few VFP forums and help out... and should you happen across someone that appears to be a little fearful about their future and VFP then take them by the hand and let them know everything is going to be alright. Lastly design some very professional apps in VFP so customers and other developers can see how great this tool really is. There's a bright and brilliant future ahead for VFP, but it is, as with all things... what you make of it.