Don't get too excited. There are a few reasons to be less than thrilled with VFP's position as a middle-tier tool:

1. Will MS improve parts of VFP that don't affect middle tier applications (especially building UIs which is a huge weakness for VFP).

2. VB is also being positioned as a middle-tier tool.

3. It's nice that VFP was used to build ADO, it's too bad that VFP doesn't work very well with ADO. This makes it much harder to pass data back and forth between tiers.

4. Unlike VB, only a single user can access a VFP COM object at once. If multiple requests are received, all but the first will be blocked meaning that VFP really processes the requests serially.

5. MicroEndeavors has been a VFP shop for a long time. I'll be optimistic when I see companies that haven't used VFP in the past start to use it.

>Hey now,
>
>I attended a two day seminar Mon & Tue by MicroEndeavors...topic was "What's new in VFP 6.O. Folks, it was one one of the best seminars I've been to.
>
>But that's not the point...point is Microsoft is positioning VFP to be the middle tier in a Three-Tier/n-Tier client-sever configuration. I guess they finally realized that if we're talking about "data", then there is no other application in Visual Studio that can come close to VFP's data-centric abilities.
>
>It was quite amazing to watch Chuck (instructor) create a VPF COM server that proceessed data and then:
>
>1. Fired it off from a VB form
>2. Create 3 instances of it running on Internet Information Server and fire them all off simulaneously via 3 running web browser windows.
>
>The fact that ADO was patterned off VFP cursor model was quite enheartening, too.
>
>Bottom line is, it looks like VFP has *finally* gotten a defined role in the future plans of Mr. Bill. Now all we need is for him to get up off of some advertising dollars.... ;)