There isn't a something/tool that can reasonablly good enough to convert a
real, sizeable VB6 app to a good .NET app (win form app or web app?). Most
likely the conversion means total re-writing after all. So, if you
converting/rewriting, why not doing it the .NET way? If I were you, I'd
either not do it at all, or do it the .NET way, if the app is important to
the business enough that is worth the converting, I mean, re-writing.
"Peter" <Pe***@discussions.microsoft.comwrote in message
news:E8**********************************@microsof t.com...
>I am involved in migrating a sizeable vb6 application to vb.net but don't
want to add the extra complexity of migrating adodb to ado.net. Is this a
sensible approach and if not what are the drawbacks?