>>>>Time for my $.02, since everyone was asking for it. :)
>>>
>>>
>>>I need to beat this horse a little more - here is the link where MS claims that the OLE DB cursor technology in ADO is based on VFP:
>>>

>>>http://msdn.microsoft.com/library/psdk/dasdk/tech1g9x.htm

>>
>>
>>Hey John,
>>
>>Does this speak volumes? <g>
>>
>PM4JI...
>
>Disclaimer: I enjoy coding in VFP. I think it is cool.
>
>It actually does speak volumes, but not necessarily in a positive light for the future of VFP. Yes, it does mean VFP has good technology under the hood. But MS chose to extend the ability of the engine OUTSIDE of VFP, rather than inside.
>
>All the best,

Steve,

Oh, I know.. I'm just taking advantage to rub JVP's nose in it a little since he's so quick the other way to read his doom & gloom opinion into VFP. <g>

As far as the technology extension being inside or outside I'd read that as not being too significant. I actally kind of expect that future versions of VFP, VB, Word, Excel, SQL, etc, will all use common objects. With things like reports and menus for example it makes absolutely no sense to me whatsoever to keep them inside each product now that MSFT is having some successes with OLE DB and so forth. In VFP's case I think that does then bring up the issue of how compatible a future version will be with older versions and wuite frankly at some point I would encourage MSFT to "de-couple" some of these items in order to gain a more universal approach.

Just makes sense to me.

Would that spell the end of VFP as we know it today? Probably, but who cares?

Best,

DD