RE: sql server 2000/adp security problem

From: JK (jkadach_at_nextdoor.org)
Date: 07/12/04 

Date: Mon, 12 Jul 2004 12:39:16 -0700

I have some good news. my problem got resolved today! :)
So I just want to drop this note to share the resolution
and wanted to say thank you, Kevin and everyone, for your
help and time :)

--------------------------------------
Part of the cause and resolution is addressed in MS
knowledge base article 313253:

"Cause: You do not have SELECT permissions on the
SysObjects system table in the database. Access relies on
the SysObjects table when it performs various tasks, such
as opening reports or determining which stored procedures
to display in the Database window.

 

Resolution:

"Grant the user (or the Public database role) SELECT
permission on the SysObjects system table in the
database. "

 

After granting the public role Select permission on the
SysObejcts system table, the user is then able to see the
objects, as well as open the tables and run stored
procedures from the adp's database window. (Btw, select
permissions on syscolumns, systypes and syscomments system
tables for other users or public role are also required by
Access adp, but this was not mentioned in article 313253.)

However, the list boxes in my forms, which uses
parameterized stored procedures still did not work as
intended.

 

With help from MS' Tech Support (team members from SQL
Server 2000, Webdata, and Access 2003 contributed), we
figured out that qualifying the database owner (dbo in my
case) or adding dbo to the object name (ie.,
dbo.procedurename) in the list box's row source resolves
the problem.

Sincerely,
Jocelyn J

 
ps. I'm also grateful to Hari Prasad, Mike Gunderloy, Paul
Schnitzler, and Danny Lesandrini. Their time, interest and
efforts are greatly appreciated! :)

>-----Original Message-----
>Yes. Try using SQL Profiler to capture the traffic when
you're using the
>ADP project.
>One of the columns in the profiler data is the NT
username. This will
>allow you to verify that the user is connected using the
correct
>credentials as well.
>
>It could be that the context of the initial connection is
being made as the
>developer and not the user you intended.
>
>Thanks,
>
>Kevin McDonnell
>Microsoft Corporation
>
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>
>
>.
>

Relevant Pages

  • SQL Server 2000/adp problem
    ... Part of the cause and resolution is addressed in MS ... You do not have SELECT permissions on the ... SysObjects system table in the database. ... SQL Server 2000, Webdata, and Access 2003 contributed), we ...
    (microsoft.public.access.security)
  • Re: Access Versus Windows NT Permissions
    ... It'll be hidden in windows explorer, but savvy users can still get to it ... in the process which inherits the permissions of the folder. ... > permissions to the folder where the database is located for a user to even ... do newer versions of Access have a resolution? ...
    (microsoft.public.access.security)
  • Re: List Users Permissions down to table.column action
    ... THIS STORED PROCEDURE GENERATES COMMANDS ... -- FIXED PROBLEMS WITH STATEMENT LEVEL PERMISSIONS GRANTING. ... -- CREATE TABLE TO HOLD LIST OF USERS IN CURRENT DATABASE ... -- GRANT USER ACCESS TO SERVER ROLES ...
    (microsoft.public.sqlserver.security)
  • Re: User access on a company intranet
    ... Yes they need full permissions on the folder where the backend is. ... You wouldn't need to do this in your copy of the database. ... However you can toggle the shiftkey bypass from another mdb file. ... When you want to implement security, you create a new mdw file, ...
    (microsoft.public.access.security)
  • Re: Active directory corruption
    ... During an installation of PHP I accidentally changed permissions for the ... Active Directory database is unavailable because it is damaged, ... Open a command prompt and run NTDSUTIL to verify the paths for the ...
    (microsoft.public.windows.server.sbs)
Loading