|
The thing started when Visual Foxpro got means of working with external databases via client-server tecnology. Many developers - as well as their customers - found it promising enough to store data in databases of SQL-Server, Oracle and MySQL.
As Microsoft - naturally - promotes it very own SQL Server by creating means for binding VFP with this product, let's stick to the point and have a look at their promotion features.
For many years we've heard many opinions on Microsoft policy which can sacrifice whole products (not the worst ones) to the altar of their strategic plans. It's evident, that FoxPro is actually a considerable obstacle to worldwide SQL Server victory as well as (and this is much worse) NET-technologies.
Microsoft may work really hard on developing ADO.NET, but if we give just a quick look to both products - and compare them - we'll clearly see that it will take Microsoft about a hundred years to introduce VFP functionality to Visual Studio.NET.
Still, let's be unprejudiced in discussing these products. Our task is to study them and find their combinations optimal for certain tasks.Well, does FoxPro need SQL Server? If it does, how much does it need it?
|
