Jim,

My view point is based on what MS does and not what anyone at MS says they're going to do. You wouldn't even know VFP existed going to http://msdn.microsoft.com. There was a blurb about the release of VFP 8.0 posted for a day or two. Now, not only is VFP not mentioned in the Key Topics but VFP isn't even listed on the Developer Tools menu on the right-hand side.

I understand your concern about the disappearing VFP KB Articles. This is a sure sign of where MS wants EVERYONE to go today.

MS, like Martha Stewart is hubris and look where it got Martha...

>SNIP
>>
>>Why would MS want to sell a VFP box for $650.00 to a developer that can create any number of applications for 50 plus users when they charge one company with 50 users $7,967.00?
>>
>>MS will NEVER PROMOTE VFP to anyone other than VFP developers.
>
>Will,
>
>While I agree that your supposition appears to be the way things really are, it is also short-sighted and somewhat contradictory (if heard with hope < s >) of statements not so long ago by but Steve Ballmer and Ken Levy.
>
>Steve Ballmer said that MS (now) realizes that the small/medium business is MS' largest potential market. That being so, one would expect that MS would coddle/groom that market to gain any of its dollars possible - especially considering MS' fear of Linux.
>Ken Levy said, just after the VFP8 beta was made public, that Delphi users were also a target for sales of VFP. I agree that evidence of such is sparse to nil, but he did say that.
>
>On the other hand, things seem afoot at MS outside the control of the VFP Team that appear to be highly detrimental to VFP's future. I (and I suspect others too) am very worried about the content of the most recent MSDN Library vis-a-vis VFP KB Articles (specifically PRB:, BUG:, FIX:, INFO: and HOWTO:) - they've DISAPPEARED!!!
>In addition, while those VFP Articles remain accessible through MSDN Online they seem to have been 'frozen' - by and large - at VFP6 despite "Last reviewed" dates on some as recent as two weeks ago.
>I don't know if other non-.NET products (e.g. VB6 and prior) have the same fate but I'll guess they do.
>Now how are we to continue to develop using VFP if those articles are all there is?
>And numerous people here have complained about consistent malfunction of the MS VFP Bug reporting site, getting all the way through entering the complete details of a bug before being kicked out with some page-not-available message#@!#@!@# This went on for months! Apparently, now that someone got a response from the Webmaster that the page had been discontinued, it is being addressed. Months after the fact!
>
>I don't know what good a VFP9/VFP10/VFP11 etc. will do us if critical details about the product, formerly available through MSDN, remain frozen at VFP6.
>
>Maybe MS has something else in mind as far as those articles and future articles for VFP is concerned and they just forgot to tell us?
>
>
>>
>SNIP