dbo for Stored Procedures

[scking]

I have developed an application and am deploying it to the customer with an Access front end. When I connect to the SQL Server with the password given to my customer using SQL Server security all the stored procedures are displayed with their full names and (dbo) appended to the end. Now my application can't find the names of the stored procedures. The twist comes when I use the developer login. After connecting using it there (dbo) is not appended. Apparently I am dealing with a permissions issue here but can't seem to weed it out. What permission, or lack of it, would cause this to happen? Thanks for your support.


---------------------
scking@arinc.com
---------------------

 

[shankel]

I've been trying to figure this out too. I even gave said user dbo on the database, and she still has dbo appended to all objects in the access data project. None of my other users are having this problem, and they have fewer permissions than her on the SQL server and database. We are using Windows Authentication.

 

[blueknot]

dbo (database owner) appears when a user other than the SQL server 'owner' (the login that created the DB) connects to the database. There are scripts for changing the owner of things, but the simpler thing to do is to simply change the calls to the stored procedures WITH the .dbo extension. This should work for both user and developer: it's actually always there but suppressed/not required when connected as the dbo.

 

[scking]

I overcame this problem a while back but I appreciate your taking the time to respond. When the code was changed to use owner.name all my problems disappears. Innocently, I believed that I could provide the other users with enough permissions to run these stored procedures but found it much easier to change the code.




---------------------
scking@arinc.com
---------------------