For the record. I have got over the problem that I had by implementing the following recommendation that I found on a web site:

10. Include SET NOCOUNT ON statement into your stored procedures to stop the message indicating the number of rows affected by a T-SQL statement. This can reduce network traffic, as your client will not receive the message indicating the number of rows affected by a T-SQL statement.