Thank you, Kevin,

Per usual, your comments are well thought out. I've been in a quandary for quite some time over the future of VFP. I am not married to the language, nor do I see the need to jump into .NET in my current situation, but down the road I know will be more difficult times for the Fox.

I grew up on a horse farm in New Jersey. All my sisters have been blooded after having participated in their first fox hunt. Thankfully that barbaric tradition has been discarded--they now let the fox go after catching it--and in some places fox hunts are banned altogether. Now I’m starting to identify more and more with the poor fox!

>Jim,
>
>>I am not the only one with these concerns. Several MM developers e-mailed me in private after my post. One of them said I have some very big balls, even if my post was well written. Some of these developers have completely built their vertical-market products on your framework. For a few of them, rewritting their applications in .NET just doesn't make sence. For others it does.
>
>I agree...you don't even see Microsoft rushing to rewrite all of their unmanaged applications in .NET. It's a huge undertaking. However, if a developer were creating a new app or was doing major rework to an existing app, then I would strongly recommend looking at .NET.
>
>>My new job, scheduled to begin next month, has no need for a distributed application or a large thin client. What the company needs is a rock-solid windows application built with a good RAD tool--Visual Foxpro.
>
>I agree that Visual FoxPro is all that, but you can build the same types of Windows desktop applications in .NET right now...some things are harder in .NET but many things are easier. My main point here is that as time goes by and Microsoft continues to spend tremendous amounts of resources on .NET (and very little on FoxPro), the gap will widen and there's no way that Fox can keep up forever. That's why I recommend that Fox developers creating new projects think *very* seriously about .NET. That said, you don't have to throw out the Fox! You can still incorporate elements of FoxPro in your .NET applications where it makes sense.
>
>>That said, when do you think your next version will be released? Can you give us a list of any new enhancements you are thinking of including, aside from the cursor adaptor class?
>
>We're not announcing a release timeframe at this point, but I will give you a list of some of the majory enhancements:
>
>* Implementing structured error handling
>* Integration of CursorAdapter with our data access classes
>* Use of new collection classes
>* Use of the Empty class where it makes sense
>* Use of Event Binding
>
>When you think about it, we automatically inherit many of the other enhancements to VFP8. Many developers are using our current version (7.1) of MM VFP with VFP8 and are already using some of these new features.
>
>Regards,