It's not how much non-linq code a developer has written - it's how much time invested in learning how to do it in the existing capabilities of ADO.NET or the List class.

That wasn't my comment with which you disagreed. But whatever.

It depends on whether there was a business requirement for them to do so.

I'm saying the developer ALREADY HAD THE CAPABILITY in another tool but was exhorted to jump to FPW because it was so much better. If tabs were a business requirement, waiting for VFP3 (and/or learning about VFP in the meantime) was a better choice than doing it in FPW in the months before VFP was released.

It's not about VFP or about NET, it's the principle of being exhorted to change to a product that does not yet have but might soon get a feature you want.

And this is an apples to oranges comparison....or more like apples to apple trees. FPW and VFP were products, .NET is a platform that is much larger by comparison.

What does that have to do with missing features?! Unless you're saying it is OK for NET to miss out some features because it has lots of other stuff?

You're speaking as if every developer has a choice on which version of a tool they have to use, and when they can decide to upgrade.

Actually it was YOU who gave examples of posters saying they would learn NET when it was ready.