[AccessD] Access 2010 Native client mystery solved

Stuart McLachlan stuart at lexacorp.com.pg
Tue Feb 28 11:16:40 CST 2012


I think he means it is not safe to assume that the native client is installed on all workstations.

-- 
Stuart

On 28 Feb 2012 at 9:05, Doug Murphy wrote:

> < Anyway, AFAICT it is not safe to use native client in Access if you plan
> to distribute the FE to workstations (most cases?).>
> 
> Is there a security issue with the Native Client? Do you have a reference?
> 
> Doug
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Tuesday, February 28, 2012 5:45 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Access 2010 Native client mystery solved
> 
> I just attempted to create a new DSN directly in Access 2010 on my new test
> VM and guess what?  No "Native Client" driver selectable for Access 2010 on
> that machine.  Yesterday I was reading that the native driver client is
> installed when you install SQL Server, thus it appears (if I am reading this
> right) that you can only use the native client driver if you have
> intentionally installed the driver on a given workstation.
> 
> How silly would that be?  One would think it would be part of the Access
> installation package.
> 
> Anyway, AFAICT it is not safe to use native client in Access if you plan to
> distribute the FE to workstations (most cases?).
> 
> I for one am defaulting to the "SQL Server" driver from here on out.



More information about the AccessD mailing list