You are right! I find VFP5 more powerful than VB, but the more important question is where Microsoft will divert it's advertisment dollar.

I would advise never relying on a single product, but have other options avaliable. For example I have written simple prototypes in VB, VFP, and DELPHI to show performance gains (VFP winnning in most unless running client server, where there seems to be a pretty close tye between VFP and DELPHI). I tend to merge several, for example I use VFP as an interface to generate requests, then use Visual C++ to manage them when using client server calls. The reason in this case in C is multithreaded and can task and manage the sql requests more than one at a time, where in VFP, and VB this is undoable, which is a shame when you have to wait for a server response when the server is only barely tasked.

In other words, have more that one hat on you hat rack!

>>I am wondering that with the release of VFP 5.0 any 'real' VFP programmer will have a need to use VB for ANYTHING? VB used is a great
coding platform & has good connection to APIs, etc. But with the release of VFP 5 does VFP have at least that much power if not more?
>
>I have the feeling this is gonna be a long thread. :)
>
>I was satisfied enough with Visual FoxPro 3 and now, from what I've heard about Visual FoxPro 5 from all you guys, I'm happier and strongly believe Visual FoxPro will turn to be THE professional development environment more and more people are gonna use.
>
>There was a point VB developers were saying when comparing VB and Visual FoxPro about the fact that Visual FoxPro was not a true Windows environment because of this FLL. Now, that we have a real DLL, what are they gonna say! Yeah.