Someone said this years ago in a previous life of this topic..."why not just take VFP call it VB, the marketing guys would like it, the VB developers would finally have a real language (and a fast data engine) and life would go on." (Les Pinter, I think)

I say, let's do it and then we can charge *huge* dollars as training consultants to all the VB guys as they struggle with their first OOPS projects. A buddy of mine is a VB guy (I got him started in programming but he decided to go VB because "everyone else is"...some gratitude) and he said to me the other day that the changes look "big". He then told me that the worst thing is that the new VB no longer has a default property and that now he has to go through his entire app (a large, vertical market app) and change all of his code. I thought he meant a default *value* for a property but he explained that this was a default *property* so that when you called:

.txtSomeField

because the default property was .Value, you could retrieve the value without explicitly naming it. What the heck kind of programming is that! I couldof guessed that was poor programming style 10 years ago.

And on the subject of "huge dollars", lets make them really huge...go for a few thousand a day and not just twice our hourly rate....not that I am bitter or anything :-)

Albert


>>>Just came from a .NET seminar. The Speaker said that VFP is dead! Is this true?
>>>
>>>By the way, I like the new look of the Universal Thread. Haven't been here for a while...
>>
>>Not this again!!
>>
>>(emoticon with teardrop)
>
>Yes, VFP is dead. Now can we move on?