>It's not that VFP can't work with other tech's - it's that it is being de-valued (is that a word) by Microsoft and now the industry leaders. I was recently at a AccountMate conference where Ken Levy was speaking. After his presentation I spoke directly with him and this is a quote "Why keep fox if there will a .NET product with very similar properies and abilities in the near future". My guess that would be VB.Net but Ken did not say. If that's not saying the end is in sight I'm not to sure what else he could of said. BTW Ken's statement was made in front of at least 5 others.

Pleaes be very careful when you try to quote me. In this case, a VFP developer was asking for the technical reasons why VFP is not part of VS .NET, and in that kind of lengthly discussion, I was asking him a serious of questions asking for his opinion, and one of them was the one you mention above. If someone says to me that they still use VFP 6.0 and I say to them in reply "Why should we keep evolving VFP after version 8.0?", and then you came here and posted just my quote, people would wonder what I was implying. The fact is, I was just asking someone a question. Please know that a question is not a statement and cannot be inferred as such.

Also, I'm certain that what you put in quotes is not an exact quote from me, meaning, I did not use those exact words 100%, and it is a summary of how you interepted what I said out of context. People should avoid quoting me unless they have a recording to know what I said for sure and they also include all of the details of the context which it was in. Or better yet, just let me make statements directly rather than having others make their memory of my statements, it helps the VFP community and my efforts. :) Thanks John.