><<
>It remembers me of the time that JVP was pushing everyone to VB6
><<
>
>Hi Walter,
>
>I was not exactly "pushing" people to VB 6. I was suggesting that people learn about it to the extent that it could be incorporated into their VFP development efforts. A few facts:
>
>1. Dealing with the Windows API was/is a heck of a lot easier in VB than VFP
>2. VB did and still does have a better intellisense model than Fox
>3. Most code samples were written in VB
>4. VB components could define and raise events
>
>I wrote a few articles in FoxTalk that discussed how to incorporate VB into your VFP applications.
>
>Having said that - .NET is more similar to VB than VFP - VB 6's lack of inheritance nothwithstanding. Like VB 6 - .NET does not have the containership model in Fox. I'll stand by the assertion that those who at least took an academic role with VB are in better shape to learn and absorb .NET than those who did not.
>
>Finally, I have been on record saying that VB 6's lack of inheritance - IMO -was not the impediment to app development that many in the Fox world claimed it to be. Inheritance is only 1 piece in a big puzzle. Granted - it is a big/important piece and I would not want to be without it. But.... the fact that I could aggregate classes to achieve much of the same results. Nonetheless, I am ecstatic about the fact that VB .NET supports inheritence.
>
>JVP

Welcome back John.

So many things in programming are like theology and in some cases it is a matter of “what is most popular” as nothing is yet perfect. .NET continues to occupy my spare time and I have enjoyed the classes I have taken. We will soon be using it at work and at age 61 I think this tool may last me until retirement – unless I have to wait until I am 70 to retire! :)

By the way OOP and VFP helped us to get our son through college (completed his studies in June) and our daughter is in her third year at UCLA. Without OOP and a good framework I would still be writing code for clients whose projects I began in 1995! :)

Tom