>>I've been arguing a lot with Ken Levy about the non-marketing of VFP.
>>I know it won't change things in a big way .Net is the thing
>>But I'm doing it mainly to let him know that we're aware of what's going on.
>>To me the worst thing would be to let it go without saying anything.
>>What I hope will happen over these complaints is that it'll keep VFP alive a little longer.
>>
>
>That is pathetic.....

Why ?

>
>>Let me state again that I know that .Net is the MS thing now. But to many developers VFP still does the job.
>>
>
>You see the writing on the wall - but will do nothing about it. WHY????

Because VFP is doing what I need it to do. No doubt in my mind that at some point I'll have to replace it with another tool. Probably more because MS will have decided that it's time for me to use something else rather than me deciding it's time to do it.

When that time comes I'll see what are the offerings on the market.

I saw cool things about .Net but that does'nt mean there are'nt cool things elsewhere.

I heard there's still life out of the .Net world <g>



>>Probable scenario without complaints :
>>
>>
>From within MS this could be interpreted has a lost of interest in the community. With a signal that clear why should we bother to keep improving VFP.
>>
>>Probable scenario with complaints :
>>
>>MS continues to improve VFP because the signal is loud and clear that VFP is still used by enough developers to justify improving it.
>>
>
>The day comes when VFP stops generating a profit - that is the day VFP will stop - feelings and sentiment in the community nothwithstanding. That is not to say it could not happen sooner.
>
>John