Hello. Excuse me if this has been answered somewhere, but I have searched everywhere.. How can I suppress the "changed database context" message? I don't think I can avoid it as one of my stored procedures uses a master stored procedure. I even tried just copying that master procedure to the database I'm working from. That gave me the same message. If I can avoid it or catch it, please let me know. I'm using SQL Server 2000 with wsh (vbscript). Is there a way to catch that "error" in my stored procedure, if it can't be avoided? Thanks!!!
I'm not sure about a .vbs file, but in an active server page, you first check the connection errors collection, then ignore everything with SQLState = 01000. That covers general warning errors.
There is no "i" in team, but idiot has two.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply