Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pgill
Starting Member
17 Posts |
 Posted - 2007-09-21 : 10:41:38
|
| I have a MS Access 97 frontend to a SQL Server 2005 backend. I am using an ODBC User DSN to link the tables to SQL Server. The users authenticate through groups set up in Windows 2003. Some groups can open the database and do everything necessary. With other groups I get an ODBC call failed error when I try to open a table. If I try the "Get External Data", "Link Tables", from the File Menu then select ODBC and the User DSN, I don't see all of the tables on the SQL Server. For some of the groups the "Get External Data" is grayed out. I have checked all permissions on the Windows Server as well as the SQL Server and everything appears to be OK. Can anyone help me with this one.Thanks. |
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-09-21 : 10:54:37
|
Have you checked with your network administrator to see if any group policy changes where made?
Future guru in the making. |
 |
|
|
pgill
Starting Member
17 Posts |
Posted - 2007-09-21 : 14:33:43
|
| Hi Zoroaster, I resolved the issue with one group of users by changing the column level permissions in SQL Server. Now I have another separate group of users that can not connect to any of the tables. By the way, I am the DB admin although new to SQL server. I don't think that there is a GP issue although I could be wrong (it's been know to happen before). What would I look for in GP? |
|
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-09-21 : 15:25:22
|
Why did you have to change the column level permissions? My question was just general because troubleshooting something like this the first question to ask is what changed? That is assuming the same users were able to access the database just fine before, if that is not the case then I suppose it is more likely that you have overlooked some permissions for the group. Have you double-checked the role permissions that the group you are having issues with is assigned to?
Future guru in the making. |
|
|
|
pgill
Starting Member
17 Posts |
Posted - 2007-09-21 : 15:50:24
|
| I changed the column level permissions because I was experimenting with them before and I denied access to some columns. I went back and granted access to those previously denied columns and the ODBC error was corrected. I have not checked the role permissions for the group, I will do this next.Thanks |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-22 : 22:16:04
|
| If you like to limit certain columns for access to user, you can create view and grant select permission to view. |
|
|
|
|
|
|
ODBC connection problem