August 18, 2006 at 5:31 pm
Hi, does anyone know why a stored procedure called from an MSAccess VBA module utilizing a SQL Server login and SQLOLEDB would cause Access to throw an error saying 'Current user does not have permission to perform that action on (some tabelname)'. All the necessary permissions have been granted to the login and will often perform have of its task before Access throws the error. Using the sa login seems to solve the issue, but I don't want that exposed to prying eyes. Any suggestions?
August 21, 2006 at 8:00 am
This was removed by the editor as SPAM
August 21, 2006 at 8:26 am
Are you prefixing the procedure name with dbo when you make the call:
.commandtext = "dbo.prMyProcedure"
How are you calling the procedure, using a command object or using the open method of a recordset object?
When you logon using the SQL Login account, can you see all of the objects the procedure uses in the Access windows, and if so, can you open them directly from there, ie. can you open all of the tables it uses?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply