[AccessD] Access 2010 Native client mystery solved

 >It should be able to be done through scripting...MS command scripting can do virtually anything to 
a host computer.

Until the Notwork guys lock down the machines... ;)

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 2/28/2012 12:40 PM, Jim Lawrence wrote:
> Does ADO OLE and its associated drivers still not work with Access? (I have
> not progressed beyond Access2003 with my clients because of such issues.)
>
> http://www.drivermanager.com/en/download-confirmation.php?Brand=Microsoft&Lo
> go=microsoft
>
> Maybe you are going to have to even install the drivers on a clients
> computer before running your application. It should be able to be done
> through scripting...MS command scripting can do virtually anything to a host
> computer.
>
> Jim
>
> -----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.
>