Raza --

Since I was a recipient for this message as well, I just wanted to say: Right on! I'm in the same boat with you -- a whole lot of people are using my VFP -based software day in day out, and it is as stable as a software can be <g>. It took me over 10 years to get here with the software, and re-writing it will take at least 2-3 years, plus introduce a whole lot of new problems AND backward incompatibilites, since .NET, for example, simply can not replicate everything I have done with VFP (and vice versa, admittedly).

To me it is not a question of which language is superior or more "modern". To me it is a question of how much time and effort has gone into this software and how much time will I and my staff have to spend to reinvent the VFP wheel now, using another language. I would gladly pay a LOT of money to have an assurance of continued VFP (or something like it) development, because re-engineering these big apps is not going to be cheap by any means, whether it is my time or money out of my pocket for some other developer's time.

I'm not whining, mind you, I am just facing a reality that I don't much like. And, so, I'm already moving on. I'm just thankful (yes, to Microsoft) that the "VFP fuse" is plenty long to allow for adjustment and re-engineering before the sun sets on VFP.

Cheers!

Pertti


>Hi Martin...
>
>First of all I would limke to thank you all of you in UT community, You are unique, very helpfull to each others.
>
>Secondly, I am not a .NET/M$ hater. I am not a person who develope for a hobby. I have developed an accounting software application with 800+ installed base. Evey moringing about 15000+ users use my application written in VFP and it works like a champ... To develope and debug an application of this magnitude, it takes 10/15 years. It took VFP a 15+ plus years to be what it is now and I am sure it will take .NET years to be where VFP is now. Now when the product is mature and almost bug free, Microsoft decided to discontinue. If VFP is not making any money then MS should change the licencing policy for VFP, limit the size of VFP tables and force us to move to SQL with VFP as front end. I am sure a lots of companies like mine would not mind paying.
>
>I have a responsibility to my clients and Microsoft have the same responsibility to us VFP developers, give us an option, charge us for the licencing and we will pay, we have invested years of our life in this product. For a business application it is a complete developement tool.
>
>Raz