Jim DeMarco
Jdemarco at hudsonhealthplan.org
Wed May 10 06:59:27 CDT 2006
Yes this is a great article. I read it a few weeks back in the paper mag and had the same thought. I've always been a proponent of writing COM objects in VB6 for use in Access apps but we stopped using VB6 for new development a few months ago. This gives us an opportunity to begin implementing processes via COM through .NET. A must read IMO. Jim DeMarco -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly Sent: Tuesday, May 09, 2006 3:45 PM To: Access Developers discussion and problem solving Subject: [AccessD] Call .Net 2.0 Framework code from Access VBA This might be interesting and is fairly simple Call Into The .NET Framework From Existing Visual Basic 6.0 Apps http://msdn.microsoft.com/msdnmag/issues/06/05/WrapItUp/default.aspx This article adresses VB6 but there is no reason, it can't be used from VBA You will need VB Express installed along with .Net Framework 2.0 to create the wrapper dll. And perhaps register as COM object. It should save you using a lot of 3'd party controls by using the NET Framework class library instead. There are a lot of things that can be quickly written in .Net The .NET Framework classes must be called through a wrapper. The wrappers are built using the COM Class item in VB Express, and they behave like any other COM objects -- Marty Connelly Victoria, B.C. Canada -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com