Re: MS Access can't find Recordsource object

From: Mary Chipman [MSFT] (mchip_at_online.microsoft.com)
Date: 02/04/05 

Date: Fri, 04 Feb 2005 18:29:06 -0500

Letting your users run as sysadmins is extremely dangerous and is
always the wrong answer when your application doesn't run correctly. I
suspect you are using Access 2000? If so, upgrading is one option
since later versions are better able to resolve queries where objects
are owned by dbo. If upgrading isn't an option, then you must prepend
the ownername to the object name as in "SELECT * FROM dbo.MyTable". If
your objects are owned by users other than dbo, it is recommended that
you transfer ownership to dbo by executing the sp_changeobjectowner
system stored procedure on those objects.

--Mary

On Fri, 4 Feb 2005 13:55:07 -0800, "Brett"
<Brett@discussions.microsoft.com> wrote:

>I have an MS Access project front end that is connected to an MSDE backend.
>For several reports and forms I have the recordset property set to the name
>of a stored procedure or a view. Everything works fine for me (as an MSDE
>sys admin). However, when other users try to open the form or report they
>get the error "Object not found" which I assume is because they cannot fully
>resolve the name. If I give those users sysadmin privileges, everything
>works fine. If I add dbo. to the front of the stored procedure or view name,
>it works fine for those users with normal permissions. I don't really want
>to do this as it would require a lot of changes both to the recordsource
>properties and to the actual stored procedures that reference objects without
>a complete name.
>I tried giving ownership of all the databases on the server to these people
>and that didn't work either. Only giving them full sysadmin resolves the
>problem.
>
>Does anyone know what permission I must grant in order for these users to be
>able to open the forms and reports?

Relevant Pages

  • Re: inconsistent report problems
    ... create statement - and add dbo. ... I'm using virtually the same code for 4 reports so far. ... is the name of the stored procedure and the list of params. ... Set cmd = New ADODB.Command ...
    (microsoft.public.access.adp.sqlserver)
  • Re: I still dont get it.
    ... > You can create a stored procedure to call xp_cmdshell to run a command. ... > though the originator has no such rights. ... > Russell Fields ... >> A has rights to sysadmin sproc, if I pass in the table to be created as ...
    (microsoft.public.sqlserver.security)
  • Re: I still dont get it.
    ... You can create a stored procedure to call xp_cmdshell to run a command. ... can be the sysadmin. ... though the originator has no such rights. ...
    (microsoft.public.sqlserver.security)
  • Re: Alter User for domain user
    ... Any member of sysadmin will always be the dbo inside a DB. ... connect to the server with Windows Authentication, the default schema ...
    (microsoft.public.sqlserver.security)
  • RE: SQL2KSP4 sp_addalias and db_accessadmin
    ... Based on my test, after installing SP4, only member of sysadmin or dbo can ... It seems a design behaviour. ...
    (microsoft.public.sqlserver.security)
Loading