I think the combination of the next version of .Net with LINQ ... (read more here: http://msdn.microsoft.com/netframework/future/linq/default.aspx?pull=/library/en-us/dndotnet/html/linqprojectovw.asp) and smaller versions of SQL Server will work out pretty well.

>Now that it is very clear the Microsoft are gradually putting VFP to bed, I wonder what new product will emerge and take it's place?
>Surely we are not going to be left with only 2 alternatives - Microsoft Access or SQL Server.
>There is definitely a market for a "middle of the road" product like VFP that is ideal for applications that:
>
> (a) Do not need something as powerful as SQL server
> (b) Are easy to deploy and have their own database engine
> (c) That are also more powerful and faster than MS Access
>
>In the past this market was taken up by products like VFP, Paradox, Powerbuilder, FileMaker etc.
>Since Microsoft does not believe that there is market for such a product anymore, are there any third party developers thinking on what will be a good replacement for VFP?