John,
>
>Seriously Walter, I like these discussions... Than can be good, and we should try to make them good. It is true that at times, I can get over-zealous.. Maybe that is an understatment.

So can I....

>I really think you need to re-evaluate you stance on VB to some extent. You have admited as much that you don't know VB that well. If you compare VFP and VB on the basis of visual classes, hands down, VFP is much easier to work with. However, there is a lot more going on than building UI's..


I know. But I'm on a standpoint that I find that UI's are undervalued by most developers. We both know the past of procedural driven applications which was a pain to work with. I try to emphasize the UI in my applications, as i'm convinced that there is still much wrong with the UI of many applications.

AS for VB I know that it is a powerfull language that is able to program things you can't do with VFP. I admit that VBA is an important part now of sofware development and I don't think I should underestimate things here.

But as I mentioned before when writing Data intensive apps I do believe VFP is the right choice. Not only does it generally require less add-ons (activeX DLLs, etc), which can cause a DLL hell, it seems to be able to get the job done more straight ahead, is generally faster, better maintainable and more flexible on the UI side.

I'll never say that VB won't be able to make good business apps, sometimes it will be a better choice than VFP, but in general I don't see much of a reason here to think into the VB (IDE !) box.

For myself I've made a choice that if I'm going to learn another language more througely it will be C++. I might even leave the MS box and look at delphi.

>Once again, we will agree to disagree....

Agreed.


Walter,