Vlad,

>Take a look to the video at the www.microsoft.com/vfoxpro page. You will be wondered. In addition, it appears that new versions of VFP will have another name ("Toledo" is suggestedfor version 8.0) - maybe that is what confused?

We know VFP 7.0 is a viable solution, but we have been told that 8.0 (Toledo) will be the last version when it comes out in 18 months. Since we are choosing tools for the 3-year-and-beyond picture, a tool that is going to be discontinued in 18 months would be out of the question (and rightly so).

>In fact it is bad to know again that VFP is still refused just because somebody hate it. I tried both VB and VFP and can tell that VFP is better and allow much more functionality. Experts in VFP can develop the little application more quickly in VFP then in VB (just my opinion).

I don't think anyone here hates it or is prejudiced against it. Some folks were told flat-out by a MS representative that version 8.0 will be the last. If that is true, then I totally agree that VFP is not the right tool to base the future of our company on. Yes, I agree that I can develop more quickly in VFP than VB (and we have a great deal of VFP expertise within our organization), but if the tool is going bye-bye then all the development speed in the world won't mean much...

I am hoping that this is a case of mis-information and that someone like Ken Levy can set things straight...

Thanks,
JoeK