>>Your point is all shared by the people of this forum. I think we all t >hink the same on this. This is why 2 weeks ago I started to be more >involved with MS people and exchanged a few emails with them. I also >asked them to state the actual position of VFP 6 because it was a common >question on the Universal Thread and that it is about time we have a >statement coming from the top. > >As far as I understand the concerned expressed here, it's not only about >"will it be a version 6.0 or not?" there will be a 6.0 version , most probably it will be released with the next release of the DevStudio the people at the fox team have already set most if not all the features for the next version (see the VFUG news section for a qoute from an Email by David Lazar) >I think it's more: what's the future of VFP on a long run, what about the >MS support for VFP, how about some good VFP books, improved documentation, >etc. Not necessarily the best news, but it seems to me that peoples want to >know something for sure, to exit from this very long incertainty. I would guess that MS would have to market VFP for the mid range, IMHO one of the problems with VFP in MS is that it doesn't requiere licenses, thus it doesn't generate as much income as a SQL Server solution. also considering the MS trend to unite the devtools into one pack, e.g. moving toward a single IDE etc. It would seems the next logical step for VFP would be to seperate the database engine from the visual designers, selling licences in packs of 10 or so , targeted to the mid range apps of up to 50 users or so. again, this is just my humble opinion (s) Arnon