I have an Access 2002 FE app with SQL server 2k BE and plan to migrate the FE to .NET
Would there be any advantage to waiting until Whidbey (VS.NET 2005) is out? If I develop Access or VB6 classes, should those translate to .NET classes

Thanks for your comment

[quoted text, click to view]
out? If I develop Access or VB6 classes, should those translate to .NET
classes?
[quoted text, click to view]

In my opinion, no.
If you've decided to go to .NET, go now and develop your classes in VB.NET.
VB.NET is very different from the "old" VB in that it is a full featured
object oriented programming language that will allow you to take advantage
of real inheritance, for example.
There *is* a learning curve associated with moving from the "old" VB (or,
VBA), so I'd go now and convert less, if I were you.
Whidbey will have new features and improvements that you can pickup on
later, at your convenience.

--
Peter [MVP Academic]