>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Seriously, I think a lot of people are going to stay in VB 6. What compelling reason is there to upgrade to VS.NET?
>
>Lack of hope for future enhancements? The knowledge that in the not so distant future, MS will stop support for the product?

>>OK - except that right now, the scales have tipped in favor
>>of staying put. It may be 2 years or so before the shift is
>>complete. No thanks, me and a lot of others are going to
>>stay out of that fray.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

me neither. In fact, many VB'ers I talk with are not planning on upgrading on Day One (or maybe even Year One!). It's imporant to point out that there's a tradition of not upgrading so quickly in VB. In the VFP community, most folks seem to upgrade as soon as the new version is available, but I haven't run into that as much with VB. Lots of folks are still using 5.0 and I know of two companies that are still using version 4. (Their loss, if you ask me... but my point is that the VB 'community' does not seem so upgrade-happy as they are stability-centric.)

I don't have any intention of upgrading my "real" work to VB.NET in the Year 2001. I will load it and play with it (probably on a separate machine) but I foresee 6.0 as my true VB development platform of choice for the next twelve months or more.