[AccessD] The future of Access, .NET and SQL

My problem is that it doesn't mean that Access programmer can *write*
managed code, only that they can use something created in another
language.  That effectively leaves Access out of the direct .Net world.

Charlotte


-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Wednesday, September 28, 2005 8:10 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] The future of Access, .NET and SQL


And your problem with that route would be?

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: September 28, 2005 6:57 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] The future of Access, .NET and SQL

"Utilize Managed code" implies .Net hooks, but I suspect that's smoke
and mirrors with Access merely using dlls created with .Net.

Charlotte Foust

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com