problem using stored procedures

I have no problem accessing sql server with the following connection string

SET conn = Server.CreateObject("ADODB.Connection") Application("dbConnect"),Application("dbUSER"),Application("dbPW")

But I cannot get the stored procedures working!! Whats wrong with the following please?

cnnStoredProc.Open="Provider=SQLOLEDB.1;Password=" & Application("dbPW") & ";Persist Security Info=True;User ID=xxxxx;Initial Catalog=dbname;Data"

the code is classic asp.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

at a first glance - nothing in particular
can you execute simple sql statements?
Otherwise your user seams to have limited access or is restricted to execute statements.

For conenction strings have a look here:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
userid=xxxx and initial calalog=dbname I hope they are not the real ones in your connect string (sorry to ask, but such things happen)

What's the problem? You cannot connect or you can connect but cannot execute procedure
When something fails there will be an errormessage that could guide you to the exact problem.

michaeldean99Author Commented:
no, they are not the real codes!

I cannot get the classic asp code to process the stored procedure. I get
Wrong number of arguments or invalid property assignment

At the moment I cannot access the online database  so I cannot establish the problem. I was checking that that my code was correct. It seems to be so I will have to wait for the dba to look at the online database.
And you're getting that message on the call of the stored procedure? Annyway then you don't get it on your connection so that part of your question is gone.

Leaves you with the parameters or their types that don't match the procedure.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.