>Dean;

>I think we are in agreement but the web sucks when it comes to attempting to communicate.

>I use VB also and have for years. When management says use this tool, I do. I like to analyze the requirements first and then give my opinion as to what I think is the best tool for a job. There are applications that I have recommended we use VB because of system requirements.

>My feeling is that VB 7.0 is a 1.0 release (which I have stated in many of my threads). Version 1.0 of any software has not been known to be “robust” (forgive that term). VB 3.0, 4.0, 5.0, 6.0, and 7.0 have had many interesting changes along the way. To me VFP 7.0 is an extension and refinement of VFP 3.0, 5.0 and 6.0. It has not had a “radical” departure from the original concepts. The product has been “on the same path” for over 6 years. To me that is important as I feel the product was well thought out at its inception. VB has been “searching” for a path. It does not have the type of history I have just described.

Well said.

I've always said, every since I started using Foxpro, that foxpro was way ahead its time. I think it says alot about a product when you can transport about 99% of the code from foxpro 1.0 to VFPx.0 and it still runs like a champ.


>Microsoft will not spend the money on VFP marketing that VB enjoys. Bashing VB is not my point. I attempt to be honest and am not interested in emotion on this topic. I think .NET is interesting and I am doing everything I can to be proficient with it. I program in several languages including C and Java. Every tool has it’s place. I have also programmed in FORTRAN. That is a good tool to “crunch numbers” on a Mainframe. Now where did I put those pesky punched cards?

I think you'll find your punch card in the Simsonian somewhere. :)


>Tom