dbo in Record Source

  • Thread starter Thread starter Andy Williams
  • Start date Start date
A

Andy Williams

I've inherited an Access 2000 ADP which I've been tasked to rewrite in VB.
It uses no security, (sa and blank password), and my first step is to secure
the SQL Server database. Problem is, when I switch over to NT integrated
security, the reports based on stored procedures cease to function. However
if I add 'dbo.' in front of the sp name, they work fine. I programmed
extensively with ADP's a few years ago and I've never come across this.

So, do I need to go into all the reports and add the dbo, or is there a way
around this. I'd like to get the database secured before I begin the new
application.

TIA

-Andy
 
Hi Andy,
So, do I need to go into all the reports and add the dbo, or is there a way
around this. I'd like to get the database secured before I begin the new
application.
Click to expand...

Yes you have to do. The prefix "dbo" is not a feature by Access but by
the sql server. It es always better to use the full qualifyer for
sql-objects
in any case.

[owner].[object]

The same is to do in VIEWS, SP's, FUNCTIONS etc in SQL-Server (T-SQL)

dbo is the owner of the object. And the application you have to
rewrite
is only working because every user was acting as dbo because he is
logged on
as "sa".

HTH ;-)

--
Gruß, Uwe Ricken
MCP for SQL Server 2000 Database Implementation

GNS GmbH, Frankfurt am Main
http://www.gns-online.de
http://www.memberadmin.de
http://www.conferenceadmin.de
____________________________________________________
APP: http://www.AccessProfiPool.de
dbdev: http://www.dbdev.org
FAQ: http://www.donkarl.com/AccessFAQ.htm
 
Back
Top