>Jeff,
>
>>At Dev-Con it was indicated that ADO.Net will not be supported in VFP 7. Now from my point of view this is a gaint step backwards for VFP. Ver 5 and 6 moved VFP closer to getting a check mark beside PLAYS WELL WITH OTHERS. Now we get slapped back again. Are there ways of working around the problem, you bet. I can think of several ways. It's the idea that here we go again with the VFP can't do that.
>
>What, specifically was named as the technical reason for the limitation, and where did the info come from? Is that same technical reason also true for VB6 and other non-.NET languages who would talk to .NET framework through the COM Interop, as VFP7 would?

No technical reason was given. I even asked if it was technical or political. I don't recall what session it was but I'm pretty sure it was one of Doug Hennig sessions. He would not answer the question directly, but I was left with the impression that it was political. ADO.net is for CLR langs only. Calvin was sitting in on the session and made no reply. As far as VB6 and others are concerned, I would guess it would be the same. Everyone out side the box would have to use a VB/C#/whatever rapper to have access to ADO.net.

I'm assumming that ADO will still be contained in VFP7 just NOT ADO.net. Which as far as I'm concerned is a big loss. ADO.net gets you out of the stupid shaped recordset biz and several other PIB problems. It works more like I think as a database person.

It's not the end of the world or anything, I mean there are several work arounds. It's just I hate to not have that option with out going outside the box.

Jeff