Your welcome. I should have clarified a little more but I had a production problem come up while I was replying to your message.

When you use ODBC to execute stored procedures, it ignores other messages from the stored procedure such as PRINT statements or records affected results, however I've found that when you use OLEDB, it causes weird errors when it recieves these messages from SQL server that are sometimes difficult to troubleshoot.


>Kurt...thanks for you help. I marked this as a Solution to my problem
>
>Mark Moore
>NTS Data Services, LLC