Hi JohnK,

Forgive me, but that sounds real odd to me...

Firstly, there has been virtually nothing done to the DBF for years now, and at the same time the "caveats" have only been growing and growing. *IF* there had been some action on DBF, thus making it a 'reasonable' excuse that other "features" just cannot keep up with the pace of change, then there might be something to this.

Secondly, at least for some of those "caveats" it is the VFP team itself that is the source of the problems. Remember we were told (as I heard it) at last DEVCON that VFP was ready for VS 6 but that it was other components which were causing release delays. So why did we end up with a non-functional MTS?... and with slower Refresh()es?... and with few UI bugs fixed in that release?... and so on??????

Cheers,

Jim N

>Hiya JimN
>
>Not at all! I'm just saying that if it's a choice of VFP being a niche product because of the DBF, hell, kill the DBF. I'd really like to get rid of all the little cavaets we run into to get VFP to work and play well with others and emerging standards. IMHO, VFPCOM is a good start....we need more functionality like that.
>
>Can you imagine how good it would be for you as a developer if you could work with ADO recordsets with *greater* ease than VB developers? Especialy in n-tier environments?
>
>
>>So, John, you're ready to write off the famous VFP **SPEED** ???
>>
>>That truly does surprise me.
>>
>>Frankly I am more sick of MS excluding VFP from new things on the basis that it is "ISAM". A poor excuse if I ever heard one.
>>
>>>The FoxPro bit could be referring only to the DBF structures. Frankly, with a little bit better support for newer database technologies, I could care less if they de-emphasized DBFs.
>>>
>>>
>>>
>>>>According to an article in the May 17 issue of Infoworld, Microsoft is planning to replace the jet database engine with a new product that integrates with SQL Server and the Office 2000 products. Microsoft's strategy is to improve the technical relationship between SQL Server and its desktop database applications.
>>>>
>>>>This is a direct quote from the article:
>>>>
>>>>"This is part of the overall move to better push SQL server data to the desktop--and [it is] using Office to do it. It is the first step in getting rid of Jet now in Access and the Microsoft FoxPro technologies," said one corporate user familiar with the company's plans, who requested anonymity.
>>>>
>>>>Although the source sounds suspicious, it is not surprising that Microsoft would take this direction. Given Microsoft's statement about its commitment to Foxpro, perhaps the company should have to answer some very hard questions at DEVCON?
>>>>
>>>>I hate to re-create this ugly thread, but we need to address this issue. When articles like this appear in papers like Infoworld, IT decision makers will automatically rule out VFP as a serious development tool.
>>>>
>>>>Regards,
>>>>
>>>>Jim Weil