Sidney,

Please explain your problem. Are you having trouble find the new stored proc named "Botec_GET_STAFF"?

What login are you using for the DB? Does it have permissions to access the DB objects?

This is the general idea in how to create a DB User account:

"EricDB" is the name of my DB.
"EricUser" is the new user account I'm creating.

use EricDB
go
-- add a password where you see xxxx below:
EXEC sp_addlogin 'EricUser', 'xxxx', 'EricDB'
GO
EXEC sp_grantdbaccess 'EricUser', 'EricUser'
GO
EXEC sp_addrolemember 'db_owner', 'EricUser'
go
EXEC sp_addrolemember 'db_datareader', 'EricUser'
GO
EXEC sp_addrolemember 'db_datawriter', 'EricUser'
GO

Eric

englere,
johno here. I'm obviously missing something obvious(?)
Could you mail your scripts so me? I've tried loading the downloads and still get the same error. My email address is: [email protected]
Thanks
John

John,

I can't give you my scripts because I modified the DB to work with a hosted website using a virtual root folder, instead of a virtual dir named "ThePhile". I've also made several other changes that aren't compatible with the code in the book. I wouldn't mind publishing my code and DB scripts if Wrox would agree, but I don't want to go that far unless it's ok with them. The problem with doing that is one of support. Who would support my changes if I don't have the time to do it myself? By staying with the book as closely as possible, you can get help from other people, also.

Do you understand my message above about the user account? Once you create a custom user account in your DB, you have to use that account to create all the objects, and use that in your connection strings. This will ensure you don't have any broken ownership chains, and it ensures that all objects are visible to that account. You don't even have to consider the issues of grants or owner-qualified object names if you do it this way.

I think people should study SQL Server a little more before tackling this book. This really isn't intended to be an introductory book for either C#/VB.NET, or for SQL Server. This is a middle-level book - you have to have a certain amount of working knowledge beforehand.

Eric

The incorrect connection String can give a lot of headache. For instance
My connection string should have been:
string connectionString = "server=SERVER\\HT; uid=sa; pwd=; database=Northwind"
but I neglected the server part with small letters and no escape character and continued getting error
System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

http://www.ravishakya.com