[AccessD] Access 2010 Native client mystery solved

This is why Windows is so wonderfully flexible and yet can be so seriously
compromised. 

If I was the Windows development team manager, the new Windows would be
built like Linux. No access to root functions unless you login; period. This
would mean that there are no automatic updates and if you do not have the
password, too bad...speak to the admin or who ever knows the password.
Otherwise, format and install again.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Tuesday, February 28, 2012 11:04 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access 2010 Native client mystery solved

LOL.  I guess.

John W. Colby
Colby Consulting

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

On 2/28/2012 1:46 PM, Jim Lawrence wrote:
> Over the years of doing system installs on various (hundreds?) clients for
> every franchise, I have come to understand that it only takes a few
scripts
> and a reboot and any security is history. I hardly knew the functionality
of
> some the scripts but as the onsite guy, doing some company's new installs,
> it was always a similar process. After all the changes were made, then a
> script was run and all the security and policies were re-introduced.
>
> Of course, no user could compromise the system but some guy like myself
> would break in, in moments. I guess that was why we were bonded and
checked
> every year. ;-)
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Tuesday, February 28, 2012 9:48 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [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.
>>
>

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