NT Authentication and MS Access

[heruti]

Hi, is there a way to integrate NT Authentication into an MS Access
front end, which uses table links to SQL Server 2000?

currently our frontend has 22 users, and uses full access SQL server
DSN links.
our IT department wants to introduce new policies which forbid:

1. write access to databases (except where absolutely necessary for the
specific user, which applies only to some of our access users, most of
them only need read rights)
and

2. using global SQL Server access logins, (Sql server authentication)

they want us to use read only only local user authentication... the
clients OS's are Windows 2000, NT4, etc...

I am trying to convince them to make an exception in my case.
I have read here,
http://dbforums.com/t654836.html
a claim that Access does not allow NT Authentication at all (but
perhaps he ment using Jet databases and not SQL server links).
even if it is possible, I smell trouble here, whenever a user changes
PC, new user, lots more maintenance than a simple uniform SQL Login for
everyone.
It would greatly help my case if I can find any MS or other internet
documents (not only web forum postings) that is relevant.

my Idea is to continue to use our full rights odbc link but lock the
Forms, Hide the table links, etc, instead.
Thanks for your help. Even merely reading...

[David Schofield]

On 10 Dec 2004 12:44:49 -0800, "heruti" <he****@lycos.com> wrote:

Hi, is there a way to integrate NT Authentication into an MS Access
front end, which uses table links to SQL Server 2000?

currently our frontend has 22 users, and uses full access SQL server
DSN links.
our IT department wants to introduce new policies which forbid:

1. write access to databases (except where absolutely necessary for the
specific user, which applies only to some of our access users, most of
them only need read rights)
and

2. using global SQL Server access logins, (Sql server authentication)

they want us to use read only only local user authentication... the
clients OS's are Windows 2000, NT4, etc...

I am trying to convince them to make an exception in my case.
I have read here,
http://dbforums.com/t654836.html
a claim that Access does not allow NT Authentication at all (but
perhaps he ment using Jet databases and not SQL server links).
even if it is possible, I smell trouble here, whenever a user changes
PC, new user, lots more maintenance than a simple uniform SQL Login for
everyone.
It would greatly help my case if I can find any MS or other internet
documents (not only web forum postings) that is relevant.

my Idea is to continue to use our full rights odbc link but lock the
Forms, Hide the table links, etc, instead.
Thanks for your help. Even merely reading...

Hi

One ref is:
Selecting the type of security validation used when logging on to SQL
Server (ADP)
http://office.microsoft.com/en-gb/as...713771033.aspx

However this is specific to ADP and "You must have SQL Server
installed on the same computer as the Access project for these
commands to work" which doesn't sound what you want.
David

[David Schofield]

On 10 Dec 2004 12:44:49 -0800, "heruti" <he****@lycos.com> wrote:

Hi, is there a way to integrate NT Authentication into an MS Access
front end, which uses table links to SQL Server 2000?

currently our frontend has 22 users, and uses full access SQL server
DSN links.
our IT department wants to introduce new policies which forbid:

1. write access to databases (except where absolutely necessary for the
specific user, which applies only to some of our access users, most of
them only need read rights)
and

2. using global SQL Server access logins, (Sql server authentication)

they want us to use read only only local user authentication... the
clients OS's are Windows 2000, NT4, etc...

I am trying to convince them to make an exception in my case.
I have read here,
http://dbforums.com/t654836.html
a claim that Access does not allow NT Authentication at all (but
perhaps he ment using Jet databases and not SQL server links).
even if it is possible, I smell trouble here, whenever a user changes
PC, new user, lots more maintenance than a simple uniform SQL Login for
everyone.
It would greatly help my case if I can find any MS or other internet
documents (not only web forum postings) that is relevant.

my Idea is to continue to use our full rights odbc link but lock the
Forms, Hide the table links, etc, instead.
Thanks for your help. Even merely reading...

Hi

One ref is:
Selecting the type of security validation used when logging on to SQL
Server (ADP)
http://office.microsoft.com/en-gb/as...713771033.aspx

However this is specific to ADP and "You must have SQL Server
installed on the same computer as the Access project for these
commands to work" which doesn't sound what you want.
David