New stored procedure inaccessible

Basic problem:  I've created a stored procedure and cannot access it through VB

I have other stored procedures inside this database which are accessible.  I've checked the permissions, owner, and type against other executable procedures and they are identical.  Assuming that my code in VB is correct, is there something inside SQL I need to do to access my procedure?

Thanks
LVL 2
4eosAsked:
Who is Participating?
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.

Brian CroweDatabase AdministratorCommented:
If you can run the stored procedure from QA then it is probably a VB question.  Which version of VB?  Post the applicable code and we'll see what we can see

BriCrowe
4eosAuthor Commented:
This is all the relevant code.  Configuration.ConfigurationSettings.Appsettings("Database") returns the correct connectionString.

Error msg:  "Could not find stored procedure 'ShipMe'..Net SqlClient Data ProviderHMP_UIHMP_UI.."

--- begin VB.net code ---
Dim ds as New Dataset
Dim arParams as New SqlParameter

arParams = New SqlParameter("@Customer_ID", SqlDbType.Int)
arParams.Value = 26

        Try
                SqlHelper.FillDataset(Configuration.ConfigurationSettings.AppSettings("Database"), CommandType.StoredProcedure, "ShipMe", ds, New String() {"Shipper"}, arParams)
        Catch objException As Exception
            Throw New Exception(objException.Message & objException.Source)
        Finally
            ds.Dispose()
        End Try
--- end ---

--- begin ShipMe stored procedure code ---
CREATE Procedure ShipMe

@Customer_ID int = null
As
Begin
      SELECT      *
      FROM       Ticket
      WHERE      Customer_ID = @Customer_ID
end
GO
--- end ---
Brian CroweDatabase AdministratorCommented:
I don't see anything wrong with your code...i am assuming that SQLHelper is a an inhouse class.  To eliminate that as the issue try the following code...


dim cmd as new sqlcommand
dim prm as sqlparameter

cmd.connection = new sqlconnection(Configuration.ConfigurationSettings.AppSettings("Database"))
cmd.commandtype = commandtype.storedprocedure
cmd.commandtext = "ShipMe"

prm = sqlcommand.parameters.add("@Customer_ID", sqldbtype.int)
prm.value = 26

try
     cmd.connection.open
     cmd.executenonquery
catch ex as sqlexception
     messagebox.show(ex.message)
finally
     cmd.connection.close
end try

I realize that this doesn't actually store the data but it should determine whether the stored procedure is accessible.

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
4eosAuthor Commented:
Thanks a lot BriCrowe.  My problem was with the connectionString (which I was nearly sure was right).  Kudos to your help and prompt responses though.  You got me quadruple checking the incorrect code.

Justin
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

From novice to tech pro — start learning today.