Donald,

Seems like we agree on the issue.

My wish to see something get started to address the issue with MS has fallen on deaf (or at least reluctant) ears.

So I petulantly, though greatly reduced, raise the problem every now and then to see if there might be a change in the general mood. Otherwise, I accept the prevailing atmosphere, though it grates every bone in my body to do so!

Cheers,

Jim N

>John and Jim,
>
>I have followed your posts and the posts of others and I decided to chime in. ( at my own risk )
>
>It is obvious that our beloved VFP is not what we want it to be and may never be. I don't think that WE can change that. MS has included VFP in VS because MS feels that VFP is a part of it. Whether it is a major part of VS or not is irrelevant. Granted VFP is, for some applications a "solution in a box". It seems to me that now the solution for applications is now still in a box just that the box got bigger ( albeit more expensive ) and there are more tools.
>
>If VFP were to be discontinued, like my beloved Clipper, then I would have to learn another way of accomplishing my tasks of bring my clients well developed apps with another tool. Are you a programmer or a VFP programmer?
>
>IMHO, I don't think that the vision for VFP from the MS perspective is anywhere near what the Fox community's vision, for the most part, is. Unfortunately we the sheep must follow the MS shepard to the un-promised land and deal with it.
>
>Discontent, however, is noted.