>Hi Tom.
>My comment was not directed towards you really, but to the general UT'ers.
>It seems like when I read a lot (not all) of comments about VB in this forum,
>it's usually in a left handed manner.
>
>Why would MS rag on their pride and joy, VB, just to promote VFP? - Fat chance.
>
>And if you or anyone else think that MS should put VFP ahead of VB, it will never happen. Thinking this way makes some of VFP developer seem bitter and that "W" word, - whiny.
>
>I use VB with some of my projects, and it does what it does pretty nicely.
>
>If I'm way off base, please read my signature. :)
>
>
>>>>I would like to see some verbiage reflecting the fact that Visual FoxPro is in its fourth generation and has had object oriented technology (inheritance, etc. )since it’s first version. Visual Basic 7.0 will in fact be version 1.0 of a new version of VB. Now how do you put that into a short sweet to the point sentence?
>>>
>>>
>>>
>>>What with all this obsession will bashing VB?
>
>>Dean;
>
>>Could you explain what you meant?
>
>>Tom

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.

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?

Tom