I am really impressed with this new (to me) capability MSFT has built. Check
out this picture:
http://www.kittest.com/AccessInterop.jpg
That's an Access form on the left, with a textbox to type your name in. Then
you click the button, and with a few lines of code you're launching a DotNet
form (on the right) which is picking up the argument you passed in. Not
shown in the picture is that you can then raise an event in the DotNet form
(including arguments) and your Access application can be listening for it
(WithEvents). There is also a Session-like name/value pairs capability for
global variables.
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/d...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.