Re: MS Access can't find Recordsource object

From: Brett Wilson (Wilson_at_discussions.microsoft.com)
Date: 02/07/05 

Date: Mon, 7 Feb 2005 08:09:02 -0800

Thanks Mary. Sounds like I don't have any choice but to modify all the
object names and stored procedures that reference objects. I guess I don't
understand why being a sysadmin allows you to resolve the object names, but a
regular user can't. Seems like there has to be some permission somewhere
that allows this. In the meantime, I guess I'll get busy prepending dbo. to
all my objects. You're right, I don't want my users running as sysadmins.

"Mary Chipman [MSFT]" wrote:

> 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: dbo. in vs generated code for stored procedures.
    ... all of your stored procedures be owned by dbo so that you don't have ... stored procedures to be owned by dbo, ... If she is not a sysadmin, ... A developer who is a db_owner can ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Help pls: Not allow users access to tables, stored procedures
    ... tables are owned by dbo. ... SQL Server MVP ... etc) is performed via stored procedures. ... correct permission for select permission on the tables. ...
    (microsoft.public.sqlserver.security)
  • Re: Preventing Injection - Client Side
    ... > In addition the program needs to read from ... Are they owned by "dbo"? ... To perform DML operations on tables, I would use stored procedures. ...
    (microsoft.public.sqlserver.security)
  • Re: Granting GRANT permissions
    ... procedures for dbo. ... > they can create stored procedures owned by dbo. ... > Members of db_ddladmin can also edit the stored procedures. ... >>that errors out saying you can't use AS when granting those rights. ...
    (microsoft.public.sqlserver.security)
  • Re: Cannot find Oracle data client
    ... We have to name parameters according to the names used in stored procedures ... So this can resolve the problem. ... Thanks for sharing your ...
    (microsoft.public.dotnet.framework.adonet)