>>
>>Rumor is that Jet will be killed and Access will become a SQL Server front end.
>
>Craig,
>
>And that's enough to let you believe that VFP is immune from "strategy" here??
>
>Let me ask again. . . Without VFP to *natively* access/ipdate your database, what do you REALLY have. . . A product that partially supports some ActiveX components, a product that claims to act as a server but really only hardly comes close (let's see it "serve" 250 users with good response time).
>
>In fact, a product which is more complicated than VB but less adept at most things.
>But it's all OK, because MS has a "vision".

Jim,

If it is true that Jet Database will be killed and making Access as front-end to SQL Server Desktop Database, then this should worry VFP'ers because the competition on MS front-end tools is becoming more stiff and confusing. And no matter how good VFP is; no matter how good VFP developers are, but if it does not get much attention and support from MS, VFP as a viable tool remains a dream to us.

Look, VFP lacks supporting manuals, and if this continues, the VFP marketplace will remain lower and there will come a time that we, as developers of custom applications, could no longer close project deals. And so, we can not blame some original VFP'ers to be skeptical about it and have to play safe by considering other tools.

It is therefore very important for MS to be sincere on their promises. We need MS to shout to the world that VFP is alive and a viable front-end tool for C/S application. If it will not happen on the next release, I myself, as a VFP loyalist for 7 years, will no longer think twice to consider other tools for me to remain competitive and live in the arena of software development.