G
Guest
I would like to be able to execute a long-running stored procedure from a
Windows Forms application. The procedure loops through about 7,000 items,
calling various other procedures along the way, and progress is displayed in
SQL Query Analyzer using the Print command. It appears that Print events are
handled automatically within the application (I assume through the
InfoMessage event) and displayed as Message windows, which quickly causes an
error. Is there a way to suppress this automatic handling, or do I just have
to create an even handler of my own which does nothing?
Windows Forms application. The procedure loops through about 7,000 items,
calling various other procedures along the way, and progress is displayed in
SQL Query Analyzer using the Print command. It appears that Print events are
handled automatically within the application (I assume through the
InfoMessage event) and displayed as Message windows, which quickly causes an
error. Is there a way to suppress this automatic handling, or do I just have
to create an even handler of my own which does nothing?