Re: permissions with sql server tables and access

From: Ezekiël (ezekiël_at_lycios.nl)
Date: 08/14/04

  • Next message: Dan Guzman: "Re: permissions with sql server tables and access" 
    Date: Sat, 14 Aug 2004 18:48:10 +0200

    Do you have an example? BOL is not very clear to me.

    "Mary Chipman" <mchip@online.microsoft.com> wrote in message
    news:k37sh0hnmit3dfkgj0hk7tn7pi8cdem6g9@4ax.com...
    > Create the view with the WITH VIEW_METADATA option, which will allow
    > users to use the view to update data. Without it, permissions on the
    > base tables are required. See the CREATE VIEW topic in SQL BooksOnline
    > for more information. If you put a Profiler trace on the Access-SQLS
    > app, you can see the exact calls that are being made. This will help
    > you troubleshoot future issues.
    >
    > --Mary
    >
    > On Fri, 13 Aug 2004 20:19:28 +0200, "Ezekiël" <ezekiël@lycios.nl>
    > wrote:
    >
    > >Hello,
    > >
    > >I need some help with implenting the following:
    > >
    > >I recently migrated from access to sql server and i now i want to use
    > >maintainable permissions on my tables, views, etc. The access database
    will
    > >serve as a front-end.
    > >
    > >I've created for testing purposes an testaccount with only a public role
    to
    > >access to my database.
    > >
    > >Now the hard part is when i want users to select and manipulate the data
    > >through views and stored procedures.I want only permissions set on views
    and
    > >stored procedures. The reason for this is because i don't want users to
    get
    > >the data directly from tables by means of linking or importing them to
    > >access
    > >or other databases. Only views and stored procedures can be used.
    > >
    > >Unfortunelately it doesn't work how i wanted to. When i open a view which
    is
    > >linked in access as a table, i'm getting a message that the underlying
    table
    > >has not the appropiate permissions.
    > >
    > >Now there should be a way to apply a maintainable security, so if i could
    > >have some advice and maybe an example on this matter i would be very
    > >thankful.
    > >
    >

  • Next message: Dan Guzman: "Re: permissions with sql server tables and access"

    Relevant Pages

    • Re: Execute Persmission denied on object sp_OACreate
      ... SQL Server doesn't check permissions on indirectly referenced objects as ... You can prevent ad-hoc execution of powerful master database procs while ... >I have a user who has execute permissions on a store procedure in a>database> which in turns executes 4 stored procedures in the master database. ...
      (microsoft.public.sqlserver.security)
    • permissions with sql server tables and access
      ... maintainable permissions on my tables, views, etc. ... The access database will ... Only views and stored procedures can be used. ...
      (microsoft.public.sqlserver.security)
    • Re: Security: Accessing data in another db
      ... If your objects are owned by 'dbo', the database owners need to be the same ... those users that have permissions to create dbo-owned objects. ... which only has execute permissions on the stored procedures. ... > permissions from AppUser and then grants execute permissions for AppUser ...
      (microsoft.public.sqlserver.security)
    • Re: Help with using bits in an integer
      ... Is your database schema already decided? ... and I found myself becomming tied up in knots with my stored procedures. ... Much better to store this information in a database table ... a permissions bit, you want some number or some other data ...
      (microsoft.public.dotnet.languages.vb)
    • Re: application roles
      ... The best way is to take advantage of parameterized stored procedures, ... stored procedures and denying all permissions to the base tables to ... >What is the recommended approach to prevent users from accessing database ... >> your client code. ...
      (microsoft.public.dotnet.languages.vb)