dbo for Stored Procedures

[scking]

I've developed a SQL Server database with an Access front end. When I connect using one password it append a ' (dbo)' to each of the store procedure names and prevends SQL from finding the named procedure. When i connect using the developer password nothing is appended and everything works normally. Although it seems to be a permissions thing I have not been able to isolate the problem. Anyone have any experiences or suggestions? Thanks for any assistance.


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

 

[DLSQL]

What version of Access? Are you using and MDB or an Access Data Project?

If an MDB how are you connecting to execute the sproc?

DL
MCDBA, MCSD, MCT, etc.

 

[scking]

Using both Access 2000 for Source Safe integration or Access XP for development. It's deployed in Access 2000 format. I'm upgrading a legacy program.

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

 

[DLSQL]

Are you using and MDB or an Access Data Project?

If an MDB how are you connecting to execute the sproc?

DL
MCDBA, MCSD, MCT, etc.

 

[scking]

It is an ADP Project and I connect my local front end to a database residing on either a local copy of MSDE 2000 or a remote copy running on SQL Server 2000. The ADP project allows me to connect using a wizard and I can connect locally using NT authentication but the remote computer is not in the same domain as our network and it is connected as a network connection through a mapped drive. The remote connection uses SQL Server authentication based on a username I created. My development database never experienced this issue but when the customer logged on and connected using a password they saw the dbo prefix even though I gave them all the permissions my developers username has. Their standard configuration is to the SQL Server 2000 through a mapped drive.






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