How to integrate Access application security with a SQL Server security

How to integrate Access application security with a SQL Server security

Post by Rong X » Sat, 02 May 1998 04:00:00



I have a SQL Server database with the Access front end. If I have an
application level security, how can I integrate with the SQL Server
security. That means if the user log into the Access application, how
can I know if he/she is an System Administrator or general user for the
SQL database?
Thanks.
Rong

 
 
 

How to integrate Access application security with a SQL Server security

Post by John W. Roche I » Sun, 03 May 1998 04:00:00


1. You can create Access security groups which correspond to the SQL groups.
In VBA you can determine  the group membership of the logged on user.
(CurrentUser())

2. Attempt to access an object you know a non-SA user doesn't have
permissions to and trap the resulting error.

3. Use a trusted connection, which will map domain logons(not Access logons)
to SQL groups. Then you can dispense with the Access Security.

Quote:>I have a SQL Server database with the Access front end. If I have an
>application level security, how can I integrate with the SQL Server
>security. That means if the user log into the Access application, how
>can I know if he/she is an System Administrator or general user for the
>SQL database?


 
 
 

How to integrate Access application security with a SQL Server security

Post by Francis Stanisc » Tue, 05 May 1998 04:00:00


In regards to the original post, I really hope you don't plan to make users SA.
I could
see making a couple DBO's but certainly NOT SA. This would open the door to
mayhem
and I wouldn't want to have to deal with that.

Francis


Quote:> 1. You can create Access security groups which correspond to the SQL groups.
> In VBA you can determine  the group membership of the logged on user.
> (CurrentUser())

> 2. Attempt to access an object you know a non-SA user doesn't have
> permissions to and trap the resulting error.

> 3. Use a trusted connection, which will map domain logons(not Access logons)
> to SQL groups. Then you can dispense with the Access Security.

> >I have a SQL Server database with the Access front end. If I have an
> >application level security, how can I integrate with the SQL Server
> >security. That means if the user log into the Access application, how
> >can I know if he/she is an System Administrator or general user for the
> >SQL database?

 
 
 

1. XMLBulkLoad Works with integrated security, fails with SQL Server security

I am running SQLXMLBulk load, but I do not always know wheteher the server
will be using integrated security or just SQL Security.  I set up a routine
to allow for this, but I can not connect with the sql security connection
string, only with the integrated security.  Has anyone else seen this?  I am
running SQLXML3 SP1, the connection string routines are below.

Thanks!

Paul

GambaDBServer = ConfigurationSettings.AppSettings("ServerName")

GambaDB = ConfigurationSettings.AppSettings("DatabaseName")

IntSecurity = ConfigurationSettings.AppSettings("IntegratedSecurity")

If IntSecurity = "Y" Then 'Check to see if we are using integrated security

GambaConnString = "provider=SQLOLEDB.1;data source=" & GambaDBServer

GambaConnString = GambaConnString & ";database=" & GambaDB &
";Trusted_Connection=yes"

Else ' If not usinfg integrated security set sql user and password
information

UserName = ConfigurationSettings.AppSettings("UserName")

Password = ConfigurationSettings.AppSettings("Password")

GambaConnString = "provider=SQLOLEDB.1;data source=" & GambaDBServer

GambaConnString = GambaConnString & ";database=" & GambaDB

GambaConnString = GambaConnString & ";uid =" & UserName & ";pwd=" & Password

End If

objBL.ConnectionString = GambaConnString

2. Cannot modify values of insert trigger

3. NT Integrated Security Without SQL Security Manager ?

4. Sql query with IF

5. Integrated security with Access and SQL Server

6. About connect oracle from jsp question!!!!

7. Application Access with Integrated Security Model

8. SQL Server 2000 Service Pack 1 Bug

9. Integrated Security & Security Manager

10. change from integrated security to nt only security

11. Changing from Standard security to Integrated security

12. How to connect to SQL Server through ADO (SOL Server uses Integrated Security)