Results 1 to 2 of 2

Thread: Rows Affected

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Jun 2000
    Location
    A caravan park in the Midlands (UK)
    Posts
    101

    Angry

    Does anybody know how to suppress the '(20 Rows affected)' messages that are given when, for example, inserting some rows into a table?

    I'm using SQL Server a Stored Procedure on SQL Server which Inserts data before joining Inserted data in a further select. When called the procedure executes the Insert, which says 'ah ha I've affected n rows'; the calling line from VBScript then receives a null recordset which sort of screws things up a bit!

    Any ideas?
    Anakim

    It's a small world but I wouldn't like to paint it.

  2. #2

    Thread Starter
    Lively Member
    Join Date
    Jun 2000
    Location
    A caravan park in the Midlands (UK)
    Posts
    101

    Talking No Worries

    It's okay no need for assistance, just come across (not literally! I'm no deviant - well not to that extent) a likkle command called 'NOCOUNT'.

    Everything is dandy now.
    Anakim

    It's a small world but I wouldn't like to paint it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width