As we know VFP as a very good development tool, I'm agree with this idea that we need to aware about our around. Our clients are asking about the back of the scene when we want to present current applications or when we are going to negotiate about new application.

.Net framework brings a very rich library and as you know .Net languages are not base on runtime .dll's file like msvbvm60.dll in VB 6.0, mscrt40.dll in C++, or our VFP9R.dll VFP9T.dll MSVCR71.dll VFP9RENU.dll GDIPlus.dll files. We can find many more tools developers in .Net nowadays. We see a lot more flexibility, extendibility, support and documents on ASP.Net, web hosting is dramatically lower in price for ASP.NET against AFP, FoxWeb, WebConnect, or ... with a lot more oppurtunity to select. In an .NET project we can have developers in a team with multiple ideas in programming languages and you can understand each other because of similarities without forcing to write in an specific languages. I know that in most cases it's not a good choice but it's possible. Start an ASP.NET web site project on VS 2005 and write each of .aspx pages in C#, VB, or J# and run them all together because of supporting CTS (Common Type System), CLS (Common Language Specification), and CLR (Common Language Runtime).

Open source tools, libraries, and portals are developing in .NET nowadays that the quantity is not comparable with VFP.

I fell in love with fox since a long time ago and I'm her lover but it's technology. As somebody mentioned that a lot came from VFP to .NET (Such as ideas for LINQ), we should consider that market demand would be base on devices which is richer in support with more available person to maintenance and fix.

Even though the head persons in Fox didn't present a clear era for future, but implicitly and with keen attention we could find the approach of them about VFP. I see some lines to insist to support VFP, it's very nice and I'm agree that VFP is one of the best but market don't think so about it! When we want to sell a product, we need to advertise, we need to have enough support from producer and it's important to hear about after sales services too, and upgrades. Does the VFP head producer do in this way now? we see encouragements to jump on .NET, it was the thing that I did but still I'm with fox too becasue of its abilities in very rapid application generation and flexibilities.

About the main title, I used both the VFP Database and SQL database and even in some application we had support for both depend on client decision, thank data layer which hide it from business and UI layers.

I learned, enjoyed, and found a lot in this thread sequence, thank you all.
Farhad