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