"Keith Kratochvil" <sqlguy.back2u@comcast.net> wrote in message
news:OKP$XYOIFHA.2564@tk2msftngp13.phx.gbl...
> It sounds like you have two security related items to consider. First of
> all, SQL Server security is the overall security mechanism that is used
> which allows a user (login) to do something. If they don't have rights to
> perform an action they don't have rights.
>
> Secondly, it sounds like you have user (member) level security as well.
> Specific members can do some things (like create, read, update, or delete
> data) and others can only read specific data.
>
> How are you going to handle the SQL Server authentication? SQL Server
> authentication or integrated security (based on the network user)? You
> could do either. Depending on which option you choose you could solve the
> "who can do what" and "who can see what" problems in different ways. You
> could handle the entire security issue within your application by coding
the
> business logic into the MS Access gui. You could also allow or deny
> specific things to each SQL Server login/user.
>
> It is possible to enforce security down to the column level if you are
> allowing direct table access. If you use stored procedures to retrieve
data
> you could only retrieve the data that the user is authorized to see. You
> could also return all rows and columns to the application gui but only
show
> the specific data that the user is authorized to see. You would use a
> different solution for each option.
>
> --
> Keith
>
>
> "Ian O'Betz" <webmaster@(NoSpam)premier-ed.com> wrote in message
> news:OOY1JFOIFHA.156@TK2MSFTNGP10.phx.gbl...
> > I've been asked to create an online database for my organization with
> Access
> > as the front end. I'm pretty good with Access and moderate with SQL. In
> the
> > database, I was told that different users need to have access to certain
> > tables and columsn in those tables. Some users need to be able to create
> new
> > users to have access. So my admin user needs to grant "grant" permission
> to
> > another user.
> >
> > The users, however, are stored in a table in the database called
Members.
> > Certain members in the Members table need to have access to the
database.
> >
> > My question(s): Where is a good place to start when designing something
> like
> > this? Is there some kind of add-in I can import and use or is there some
> > other direction I should be headed? Any direction is much appreciated.
> >
> > --
> > Ian O'Betz
> > Clear Results
> > www.clearresults.net
> >
> >
> >
>

"Mary Chipman [MSFT]" <mchip@online.microsoft.com> wrote in message
news:us9h21hlcar8v0i7lloc7248kmp3vs26j6@4ax.com...
> Did you use the built-in user-level security with Access? If so, then
> SQL Server security works much the same way, with the ability to add
> users to groups (called database roles in SQLS) where they inherit the
> permissions granted to the role. You never want to grant permissions
> directly to users because it becomes an administrative nightmare.
> There are good resources on MSDN, see
> http://msdn.microsoft.com/SQL/sqlsecurity/default.aspx to start with.
> The major difference is that SQLS security is actually effective, and
> failure to implement it correctly can compromise more than just the
> database, so you'll want to learn as much as you can and plan
> carefully before forging ahead.
>
> --Mary
>
> On Fri, 4 Mar 2005 10:40:41 -0700, "Ian O'Betz"
> <webmaster@(NoSpam)premier-ed.com> wrote:
>
> >I've been asked to create an online database for my organization with
Access
> >as the front end. I'm pretty good with Access and moderate with SQL. In
the
> >database, I was told that different users need to have access to certain
> >tables and columsn in those tables. Some users need to be able to create
new
> >users to have access. So my admin user needs to grant "grant" permission
to
> >another user.
> >
> >The users, however, are stored in a table in the database called Members.
> >Certain members in the Members table need to have access to the database.
> >
> >My question(s): Where is a good place to start when designing something
like
> >this? Is there some kind of add-in I can import and use or is there some
> >other direction I should be headed? Any direction is much appreciated.
>

<webmaster@(NoSpam)premier-ed.com> wrote:

>I've been asked to create an online database for my organization with Access
>as the front end. I'm pretty good with Access and moderate with SQL. In the
>database, I was told that different users need to have access to certain
>tables and columsn in those tables. Some users need to be able to create new
>users to have access. So my admin user needs to grant "grant" permission to
>another user.
>
>The users, however, are stored in a table in the database called Members.
>Certain members in the Members table need to have access to the database.
>
>My question(s): Where is a good place to start when designing something like
>this? Is there some kind of add-in I can import and use or is there some
>other direction I should be headed? Any direction is much appreciated.