>Situation in Canada is the same, like a year ago in Bulgaria. After a year most of the clients will explain to my FoxPro colleagues that VFP8.0 is obsolete technologies and they like .Net application for thei new IS. That is the reason I to ask for VFP.Net

Yes, some bad mouths also told that since a big 10 years. And, that includes people from various companies at various levels.

Despite the fact that there is some major restructuring consideration and that it could be difficult to keep VFP's power as is and also make it VFP.NET, I also would like it to be done like that. I believe there could still be a posssibility of having a VFP 9 version, for example, to continue to be as is, with more features and functionalities, as well as being part of .NET such as VFP.NET. That would then change the entire minding of all the bad mouths as well as the clients who would start to reconsider using VFP for what it would fit best at. Thinking of that more, that would solve a lot of problems. I guess I should say, that would solve A LOT OF PROBLEMS. But, then again, if the VFP interface and engine is so strong, who would use C# and VB.NET?