[AccessD] Paean to the Access Development Team

The problem is I don't know what is the official authorized way with
   NetFramework 2.0
1. You can get at the comclass templates with Visual Studio 2005 Team 
version
2. You can create an Access Managed AddIn with Access 2007 and
    Basic Visual Studio 2005 which contains VB.Net Standard plus Access
     VSTO 2007 (which has not been finally released). This allows you to use
      the Shared Access AddIn wizard and finally the SharedAddInSetup
      Wizard that allows distribution via an .msi file with the VB.Net code
    See Getz's explanation
      Creating Managed Add-ins for Access 2007 
       http://msdn2.microsoft.com/en-us/library/aa902693.aspx
3. The method I use with VB.Net Express and 2 comclass template files
     I got from an MSDN site.  However to install via GAC you have to
     use an  install.bat to register the dll with  regasm and gacutil to
     remove any previously named dll and reinstall in the registry.
     I don't know how licit this method is but it works with Access 2003.
     and doesn't require additional software.

artful at rogers.com wrote:

>Agreed, Marty, and hats off to you for discovering/illustrating this mind-meld. My point was that MS does not make this transparent, and it takes guys like you to point it out. You should be on the MS payroll! On the other hand, if you were, then how much of your exquisite insights could we trust? 
> 
>Arthur Fuller
>Technical Writer, Data Modeler, SQL Sensei
>Artful Databases Organization
>www.artfulsoftware.com
>
>
>
>
>----- Original Message ----
>From: MartyConnelly <martyconnelly at shaw.ca>
>To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
>Sent: Monday, January 29, 2007 6:39:53 PM
>Subject: Re: [AccessD] Paean to the Access Development Team
>
>
>One thing you can do is call VB.Net or C## framework code
>from Access via a COM class wrapper creating a tlb and dll.
>
>Not that difficult if you need to merge the two code bases as some 
>things are easier
>and quicker to write in dotNet like Web Services and xml reader classes
>
>Some standalone .exe files still required a runtime install with VB6 and 
>VB.Net
>requires the dotNet Framework installed.
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada