I agree that MS is standing behind VFP and rolling out new versions just lacking in the media coverage. I know they would never mess with the VB masses and try to convert them to VFP, it wouldn't make sense. Your advice on VB is already in the works. I will be working with VB, SQL Server 7 and Access as my main tools within PB from now on. I switched divisions and they don't allow us to use VFP. I can use it for my own utilites, but not to deploy to end users.
Just passing on thoughts and observations. VB is good for my future, so I have not regrets having to use it.

Regards,
Scott Fitzgerald


>I see the problem you are facing. One thing that we all must do is to differentiate our personal needs with the needs of a company to follow the prevailing trends in development. VFP is best deployed as a single/two-tier application development tool. Forget the OO aspects of VFP and concentrate on the DML language. The integrated data engine and DML are VFP's real strengths. Yes, OO is great, but if OO was perceived as all that important in the general development environment, VB would have been dumped years ago. In fact, you can employ many OO concepts in VB. Inheritance just happens to be one of those things that you cannot employ fully. Clearly, the masses out there don't care. So, banging the OO drum for VFP falls on many deaf ears, and the rest of the folks out there say "So what...".
>
>All of that said, I use VFP, love VFP, and think for many tasks, VFP is about the best tool out there. MS cannot afford to go out there and say 'Hey, start using VFP'. No way MS is going to mess with the VB franchise.
>
>In many ways VB is better positioned for multi-tier developer. Consider VBScript and VBA, and we find that VB is firmly entrenched. Many folks just stop at the VB environment itself. I look at all 3 when defining what VB is.
>
>Finally, I don't agree that MS is not standing behind VFP. Yes, they don't push VFP over VB, but that is not the same as totally abandoning the product. If they did, we would not see VFP 6 or VFP 7, which has been promised. VFP and VB can work well together. If I were you, I would look at this as an opportunity to get up to speed on VB. That can never hurt...
>