>>snip
>>
>>Jon,
>>
>>These 'future of FoxPro' discussions are, for the very vast majority, fuelled by:
>>
>>1) rumor - 98%
>>2) absence of VFP in various MS promotions - 1%
>>
>>While no one here can state categorically that VFP will have several future versions, look at it from the other perspective. . .
>>
>>We know that VFP 7 is under development. We can therefore speculate that it will be released.
>>
>>Even if MS were to "drop" VFP after version 7, they cannot do so immediately and without recourse - they have to provide substantial on-going support and, most probably, assistance in some form to go to (their) recommended alternative(s).
>>
>>So VFP, at a minimum will be viable for 3+years - at MINIMUM.
>>
>>I don't think you have anything to worry about if you choose VFP.
>>
>>Jim N
>>
>>
>Jim,
>
>I am encouraged by what I am hearing here.
>
>Part of my concern is what I have been hearing in regards to corporate acceptance of projects done in FoxPro. If I develop a commercial system in VFP (and I realize SBT has one already) I am going to have to explain to my resellers why it isn't written in Access (since that is what they have gotten from us before) and how they can still write add-on's for it even though they don't know VFP.

Jon,

The upside to this is you'll probably add a host of new resellers.

Bill