Craig,

>>- VFP will never have the hundreds of thousands
>>of developers using it as it did back when VFP
>>6.0 was released.

Are you only including users in North America? I am betting that there are many more users out there than you might think. The majority no longer reside in the U.S.A.

>>- The core product won't have significant updates.

This is immaterial IF we get a true .Net compiler. Microsoft has stepped out of the ring.

>>- The number of conferences again shrunk this year (FoxForward
>>won't be held). There is signficant content change for both the
>>Prague and German DevCons over previous years. Both are adding
>>more .Net and/or SQL Server.
>>- Both FoxPro Advisor and FoxTalk have stopped publication.
>>FoxRockx is great, but has a limited life span.
>>- The number of posts on all the Fox related forums I visit
>>seems to be down again this year (my perception).

These statements are comments about the current state of things which I agree is dismal... Then again, that was the point of the post to begin with.

>>- Corporate use will continue to decrease. We no longer have
>>Fox development going on here.

In reality, most of what we can say here is conjecture. Stock traders go broke all the time trying to guess what the market will do. It will be interesting to see what the future holds.

>>- The Internet, and in particular, RIA, continue to rise in
>>importance. While you can use VFP on the web, using it for
>>RIA may be difficult if not impossible. Finding hostig
>>companies willing to allow you to use VFP is already difficult.

This assumes the current state of the software (No VFP Compiler for .Net).

Incidentally Craig you still have not said, other than your above comment about the web, what it is that makes you believe that VFP is so inadequate.

Thanks,

Steve