Re: SQL Server View needs permission on underlying tabel

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 06/30/04


Date: Wed, 30 Jun 2004 08:18:22 -0500

You might run a SQL Profiler trace to see if Access it using the underlying
tables directly instead of the view.

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"lars" <cld@stratek.se> wrote in message
news:DF37F7FC-094C-4CE9-911B-3292793E72A7@microsoft.com...
> Thanks Tony,
> 1. Yes, I have checked the Green Ticks, It's OK.
> 2.  Both the table and the view are owned by dbo.
> 3. I suppose the View works as it should since i works with SELECT and
UPDATE permissions on the underlying table.
>
> When I try to update the view I get the error message: UPDATE permission
denied on object <TableName>, databas <DatabasName>, owner 'dbo'.
>
> I more and more feel that it must be a bug in SQL Server or the ADO
connection.
>
> /Lars
>
>
> "Tony C" wrote:
>
> > A few things could be preventing this...
> >
> > 1.  Check the permissions for the View and ensure that you
> > are not revoking access by ensuring that access is
> > definately granted (the Green Ticks) for the users you
> > want to give the appropriate permissions to the view...
> >
> > 2.  Does the owner of the View also own the Table?  If not
> > then you may be suffering from a broken ownership
> > problem.  The best way to resolve this and all future
> > issues is to ensure that the owner for all items in SQL
> > Server is set to "dbo".  Note!! Be careful if you have to
> > change the ownership otherwise you may create other broken
> > ownership chains with other objects!!!  Consult with other
> > on-site developers on this issue.
> >
> > 3.  Are there any Columns in the Table that you have not
> > specified in the View, but require data to be in them?  If
> > so then you will need to ensure that a Default Value is
> > declared for any of these Columns in order for the View to
> > work.
> >
> > HTH
> >
> >
> > Tony C.
> > >-----Original Message-----
> > >Hello!
> > >
> > >I need to set UPDATE permission on a view without setting
> > UPDATE permission on the underlying table. I have read
> > that this should be possible but it does not work in my
> > Access 2002 project using ADO connections. Why? I use SQL
> > Server 2000 and ADO version 2.7.
> > >
> > >/Lars
> > >.
> > >
> >


Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)