Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ADO calls to stored procedure

Status
Not open for further replies.

umeman

Technical User
Oct 2, 2001
59
US
Hi,

I have a VB6 application where I am calling a SQL Server 2000 stored procedure.
When I execute the stored procedure using query analyzer
it works fine, however when I executed from the VB
application using ADO it would execute and fail somewhere.

I removed all my print statements and set nocount on and the stored procedure executed fine.
So it seems that some buffer is running out of space.


Is there any coding consideration that I need to make
when calling a stored procedure that has debug
print statements.

Thank you
 
<Is there any coding consideration that I need to make
when calling a stored procedure that has debug
print statements.

This is a little hard to follow. I'm unaware of any Transact-SQL statements that can access the VB Debug window. I suspect you mean something else.

Perhaps you could simply give some detail about the problem you're encountering, including precisely where in your code that you're getting errors. If you do this, someone is more likely to be able to figure out the problem and explain it.

HTH

Bob
 
The biggest problem I usually see with SP's, is with data types and parameters being passed in.

You can run it from query analyzer in this way:

exec spMyStoredProc 'param1', 'param2'
(no single quotes for number params)

and see if it fails.
If you have no parameters, it's a different problem obviously. Post the piece of code where you call the SP, so we can see if there's anything not right.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top