When DotNet first came out MSFT had a "conversion kit" that supposedly could
take your VB applications and convert them to DotNet. It didn't work very
well, and was probably doomed from day one. This new capability makes a lot
of sense to me, because now you can migrate an application one form at a
time and take as much time as you want for the conversion, and build the
infrastructural pieces (e.g. data access, error handling) exactly like you
want, not how some tool decides you'll want it.
The Interop Forms Toolkit is here:
http://www.microsoft.com/downloads/details.aspx?familyid=934de3c5-dc85-4065-9327-96801e57b81d&displaylang=en
It is positioned as a tool for VB6 apps, but as you can see it works for
Access as well. Not too surprising, since it is a COM-based solution.
-Tom.
Rich
*** Sent via Developersdex http://www.developersdex.com ***
Bob
-Tom.
"Rich P" <rpn...@aol.com> wrote in message
news:471795e6$0$3576$815e...@news.qwest.net...