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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-10-30 : 08:27:13
|
| David writes "I have a follow up to one of your responses to a question. It was :Update:An alert reader named Jeffrey notes some things to be wary of using Application Roles. He writes:You should note that the use of AppRoles with ADO is problematic since the approles is strictly a SQL Server concoction that ADO is apparently not aware of or programmed to.In some cases ADO will create additional connections behind the scenes (especially when connections are 'busied') and since it doesnt know about approles they are not propogated automatically to the cloned connections. As a result, the new conenctions cannot access the database through the approle and would rely on whatever other access permisions the user had. Well, I believe I have all my ducks in a row for our SQL 2000 application role for one of my databases. I open the connection with a SQL server login and password using ADO, then run the sp_setapprole proc which runs properly, but at that point, my application (VB6) cannot see any of my stored procedures that I created even though I gave the app role permission to EXEC them. Is this problem related to the above readers note ?" |
|
|
|
|
|
ADO and application role