lol Jay! No, its not a topic for me, hot or cold! Its a bit tongue in cheek. If Ken doesnt want to answer thats fine by me. My future is not dependent on VFP per se, one way or the other (as much as I do love it though). Cheer up Jay, life's good. Go to a VFP user group meeting :)

I should add: I am a big VFP supporter and will continue to develop apps in VFP for the foreseeable future within my business area. It just suits my needs perfectly :)


>No, you didn't, and I didn't say you did. My point was simply that he won't answer some of those because of the direction MS is going. This topic a bit of a button for you?
>
>>I didnt say they should did I? I even went so far as to answer that one point iro .Net. I am more interested in the other questions.
>>
>>
>>>There is no way he can answer some of those. MS is not going to market VFP as a tool over their .NET products. Assimilated into .NET, sure, but not on its own.
>>>
>>>>Just for the sake of total clarity may I break down my post into its component parts so that you (MS) can just specifically address each point for me: