REMOVE A MESSAGE

  • Thread starter ashraf_al_ani via AccessMonster.com
  • Start date
A

ashraf_al_ani via AccessMonster.com

Dear All

when I execute a stored procedure i got a message" the stored procedure has
been executed succesfully and didnt return a value"

is there a way to execute the SP without appearing this message??


best regards
 
A

ashraf_al_ani via AccessMonster.com

Dear Mary
yes iam taglking on sql server and my code is

CREATE PROCEDURE dbo.P1(@INV_SEQ nvarchar(50))
AS UPDATE dbo.P0
SET PP = 1
WHERE (inv_seq = @INV_SEQ)
GO

when i execute this code
ive got that message "the stored has been executed successfuly and didnt
return any value"
so please what change can i do in order to remove that message??

best regards

If you are talking about SQL Server, then the first line in the sproc
should be "SET NOCOUNT ON", which will suppress what is known as the
done in proc message. Here's the link to the SQL BOL topic that
describes how it works:
http://msdn.microsoft.com/en-us/library/ms189837.aspx

--Mary
[quoted text clipped - 4 lines]
best regards
 
B

Bob McClellan

As Mary said ... add "SET NOCOUNT ON" as the 1st line in your procedure.

ashraf_al_ani via AccessMonster.com said:
Dear Mary
yes iam taglking on sql server and my code is

CREATE PROCEDURE dbo.P1(@INV_SEQ nvarchar(50))
AS UPDATE dbo.P0
SET PP = 1
WHERE (inv_seq = @INV_SEQ)
GO

when i execute this code
ive got that message "the stored has been executed successfuly and didnt
return any value"
so please what change can i do in order to remove that message??

best regards

If you are talking about SQL Server, then the first line in the sproc
should be "SET NOCOUNT ON", which will suppress what is known as the
done in proc message. Here's the link to the SQL BOL topic that
describes how it works:
http://msdn.microsoft.com/en-us/library/ms189837.aspx

--Mary
[quoted text clipped - 4 lines]
best regards
 
A

ashraf_al_ani via AccessMonster.com

Dear Mary

I added the statememt asyou said but the same problem happened

error 111 i got ??
what the solution

Bob said:
As Mary said ... add "SET NOCOUNT ON" as the 1st line in your procedure.
Dear Mary
yes iam taglking on sql server and my code is
[quoted text clipped - 25 lines]
 
S

Sylvain Lafontaine

Maybe it's time for you to show us the code or the way that you're using to
call this stored procedure?

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
(French)


ashraf_al_ani via AccessMonster.com said:
Dear Mary

I added the statememt asyou said but the same problem happened

error 111 i got ??
what the solution

Bob said:
As Mary said ... add "SET NOCOUNT ON" as the 1st line in your procedure.
Dear Mary
yes iam taglking on sql server and my code is
[quoted text clipped - 25 lines]
best regards
 
A

ashraf_al_ani via AccessMonster.com

Dear All

my code for the stored procedure is

CREATE PROCEDURE dbo.P1(@INV_SEQ nvarchar(50))
AS UPDATE dbo.P0
SET PP = 1
WHERE (inv_seq = @INV_SEQ)
GO


Sylvain said:
Maybe it's time for you to show us the code or the way that you're using to
call this stored procedure?
Dear Mary
[quoted text clipped - 10 lines]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top