Permissions problem between access 2000 and sql server 2005 with stored procedures

We recently updated our database from sql server 7 to sql server 2005. We use access as a frontend for our main application which exists on a terminal server.

When I log into the terminal server as an admin and open the application; the stored procedures work fine. When I log in as a normal user most of the storedprocedures fail. Also when I am logged in as a user access renames the stored procedures and adds a ";1" at the end of them or adds a prefix of "fn" or "dt".

Obviously this is some sort of permissions issue, however we do not know where to change the permissions for this.
kikimayhayAsked:
Who is Participating?
 
kikimayhayConnect With a Mentor Author Commented:
We seem to have stumbled across the issue apparently the issue is more centered around one of our terminal servers acting up (will be completely rebuilt in the next day) not anything to do with permissions.
0
 
Raja Jegan RConnect With a Mentor SQL Server DBA & ArchitectCommented:
While creating the procedure, use EXECUTE as OWNER keywords to get rid of failing execution of Stored Procedures.

Or else you can issue on all procedures

GRANT EXECUTE ON procedure_name TO user_name;
GO
0
 
Marten RuneConnect With a Mentor SQL Expert/Infrastructure ArchitectCommented:
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
dwe761Connect With a Mentor Software EngineerCommented:
I'll try to help you but can you give a bit more info?  Do you know if you are using Windows Authentication or do you use SQL Logins?

Are you using Access ADP's or MDB or MDE or???

What permissions are you using on the Access side?

Where are the stored procedures being renamed?
0
 
kikimayhayAuthor Commented:
We use mixed mode authentication but in this case all of the users are getting access through windows authentication.
We use ADP's
The users login into access via a login in screen (username and password is identical to their windows login) so in essence windows authentication once again to access the sql.
The only place the stored procedures names change is in the access adp logged in as a user. If I log in as myself (administrator) the stored procedures are named correctly.
0
 
kikimayhayAuthor Commented:
Trying to follow link from Microsoft from Marten Rue link from above and link no longer exists.
0
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Glad to hear you solved it.

If you want to read up on the security model.
Here is another link: http://msdn.microsoft.com/en-us/library/ms189121.aspx

/Marten
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.