>I don't think so. This is an incremental change in VB. A VB developer can use these enhancments or not at his/her discretion. With the FP to VFP shift, you couldn't do things as is. Even if you didn't want to learn OOP and the other VFP enhancements, you had no choice but to use the new power tools, et al.
But don't you think there's going to be a rush to "try out" all these new toys, and a percentage of VB'ers will certainly be in over their heads? I certainly do. And if they
don't try> to use the new stuff, they're certainly going to get left behind.
>
>Also, you are going to have all gazillion VB object "how to" authors spinning out books on the new stuff ASAP. Deborah Kurata must have smoke coming off her butt right now.
>
I'm sure that will be a help, but I still feel there will be many that will never "get it".
>>Gee, might not this have the same effect on the total number of VB programmers like it did when VFP was first introduced? I remember DevCon '95 when VFP was introduced. You could see the terror in some of the attendees that they just weren't "getting" it. It was like deer caught in headlights. What was the popular phrase from back then? Oh, yeah, it was "this ain't your father's dBase".
>>
>>Let's step back and enjoy a similar show for the VB masses...