Right. Well, if M$ dumped VFP one day and I moved to VB, I'd use an Oracle back end just to spite them :-)

>Colin,
>
>The difference is that VB requires SQL Server which is per seat (or per server) licensing. VFP has "unlimited runtime distribution".
>
>It don't take a very big calculator to figure the difference there.
>
>honestly - and some out there may really jump on me for saying this, but I'd be perfectly willling to pay (have client's pay) for runtimes of VFP if it would mean a serious jump in internal support, marketing, etc. of VFP.
>
>Ken
>
>>Now I know the "they won't market VFP over VB" arguement but what I don't understand is if a developer decides to buy VFP over VB, what's really the difference to M$'s bottom line? In fact wouldn't it be better for M$ to push more VB people to VS?