I must admit that I am SOOOOOOOO dissapointed. Who Moved My Cheese? :o) Ideally, we would have bitten the bullet and included VFP in dotnet back when. That didn't happen. Get on it with it (and we pretty much did). Now we'll get over this as well after we're done moaning and groaning about it. However, it's hard to complain too loudly when there are alternative excellent and FREE (express) development tools available from MSFT...


>FWIW, I never heard that about SQL Express... They did say that about the dev Express SKUs, then changed it to forever.
>
>yag
>
>>>>There just isn't enough revenue to be made from VFP when compared to .NET / SQL Server.
>>>>
>>>>Howeever, Jamie, consider this. If a business is running a VFP app, it means they also have Windows as their OS. It also probably means that they have MicroDoft Office installed. And many VFp apps are using SQL Server as their data store. So, you see, VFP indirectly makes money for Microsoft on other things < s >.
>>>
>>>
>>>T'is true. But they will have all of those things anyway with .NET apps and also they are pretty much guaranteed of some SQL licenses as well.
>>
>>That won't hold up in the real world. I have plenty of customers that don't have a SQL-server license.
>>
>>Before anyone says "just use SQL-Server Express", note that the last conversation I saw said it would be free the first year. After that, they wouldn't commit.
>>
>>I can't seriously recommend my clients make business plans based on that.