>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.

Part of that is because the VFP crowd _can_ upgrade without breaking stuff. If I remember correctly the upgrade from VB4 to VB5 broke backwards compatibility did it not? And VB6 to VB.NET is breaking backward compatibility in a _huge_ way. VB as a language has not been nearly as stable for the last few upgrades as VFP has, so the difference in upgrade practice between camps is not surprising.