Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

odbc access - not visible tables

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
AHartman - 03 Jul 2008 00:58 GMT
I'm running Sql2005 sp2 and created a couple of tables within there own
schema(for security reasons). I then created a group within AD a gave that
group  read/write/update permissions those tables within that schema. I then
have my users try and connect to the tables via Access an ODBC connection
but the users can't view the tables They don't show up in the list of tables
is that becuase there not in he dbo schema?

I also posted to the Access forum

any thoughts?

Thanks
Linchi Shea - 03 Jul 2008 02:49 GMT
ODBC connection wasn't setup to use the credential of anyone in that group.
You can check the login credential of the ODBC connection with the following
command:

cmd>osql -D<your DSN>
>select suser_sname()
>go

Linchi

> I'm running Sql2005 sp2 and created a couple of tables within there own
> schema(for security reasons). I then created a group within AD a gave that
[quoted text clipped - 8 lines]
>
>  Thanks
AHartman - 03 Jul 2008 03:23 GMT
This ODBC connection is created on the client workstation an used normal
Windows authentication. They have access to the database to see other tables
but these new tables in schema

demand are not visiabe to them.

> ODBC connection wasn't setup to use the credential of anyone in that
> group.
[quoted text clipped - 23 lines]
>>
>>  Thanks
Mary Chipman [MSFT] - 03 Jul 2008 17:00 GMT
I don't know what your security design is, but check the permissions
granted on the schema and on the tables for the database role that
you've added the users to. I assume the public role has no
permissions. Access will not display tables that the user does not
have permission on, which is why they don't show up in the UI.

--Mary

>This ODBC connection is created on the client workstation an used normal
>Windows authentication. They have access to the database to see other tables
[quoted text clipped - 29 lines]
>>>
>>>  Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.