[AccessD] Classes In Referenced MDE

Andy,

I don't think he's talking about legal in the justice system sense, but
rather in the "development environment" sense.  There is nothing illegal
about modifying a class to be visible outside of the library, it just isn't
approved of by MS.  We don't know why but in terms of lawsuits, that won't
happen.  MS is basically saying "you can't sue MS if it doesn't work"
because they told you not to try it.


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
Sent: Wednesday, December 12, 2007 9:45 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Classes In Referenced MDE

Only wish I knew what any of that meant Shamil. :-(

It's looking fine as is now anyway. If what I've done isn't legal I'm
relying on you all to keep schtum. :-)

--
Andy Lacey
http://www.minstersystems.co.uk



--------- Original Message --------
From: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Classes In Referenced MDE
Date: 12/12/07 14:59


Andy,

Just wanted to note that another legal option could be to move your code
into VB6 ActiveX dlls...

....or even into VB.NET COM-exposed classlibs in the case your customers'
PCs
do have .NET framework installed...

....for the latter case there could be (quite some) overhead while getting
through CCW (COM Callable Wrappers generated by TLBEXP) and therefore for
the often used library functions moving code to VB.NET classlib(s) could
become inefficient....

--
Shamil