Managed Store Procedure does not deploy

I have created a managed stored procdure in a sql server project in VS. I have put in the corect server name password and login fro the connection to the database.

When I deploy however it doesn't deploy the stored proccdure to the database even though it says it has successfully deployed the stored procedure. Has anyone had this

problem and how can you make sure it is deploying to the correct database.

Did you make sure it is deploying the stored procedure into the correct database? It might be deploying it in master.mdf.

sql

Making a new ms access project

I'm having trouble making a new ms access project.
MSDE is running.
I run the wizard and it asks for a user name and password for the new
database. I put in sa and leave the password blank. Then I get an error
message.
What should I do?
Thanks.
Also, do the tables actually reside on in the sql file and the project
links to them? Where is there a tutorial on this?
Thanks again.
I found out the the Symantec Personal Firewall was blocking this.
Which program do I need to have it allow to have access? Ms Access?
Thanks.
"SAC" <someone@.microsoft.com> wrote in message
news:%23F2BGbG6EHA.3616@.TK2MSFTNGP11.phx.gbl...
> I'm having trouble making a new ms access project.
> MSDE is running.
> I run the wizard and it asks for a user name and password for the new
> database. I put in sa and leave the password blank. Then I get an error
> message.
> What should I do?
> Thanks.
> Also, do the tables actually reside on in the sql file and the project
> links to them? Where is there a tutorial on this?
> Thanks again.
>

make a user for the database

hi
how can i make a user give it a name ReportUser and a password msdn for a certain database named on the sql server 2000 and thank you for your help and oyur timeWissam,
Let's say you have a database on SQL2000 with the name, WEBDATA.

1. Make sure your SQL Instance allows SQL Server and Windows authentication enabled
* From Enterprise Mgr, right click on your server icon, and select Properties
* In the SQL Server Properties window, and select the SECURITY tab
* Check SQL Server and Windows authentication
* You will be prompted to restart the SQL Server service - go ahead and do it (just make sure you are the only user on the databases that are running on that sql instance)
2. Create a new Login User, by going in to the SECURITY - Logins and right-click to create a 'New Login', we can call it ReportUser
3. Once that new Login is created, give it the appropriate permissions for ReportUser to access only the databases you want it to touch, as well as triggering stored procedures, etc.

I didn't want to give you all the answer, but just enough to get you rolling! :-)

Happy Learning

raj