Execute Stored Procedure Failed via OLEDB Connection

[#1]

Hi experts,

I'm able to get data from a stored procedure using ODBC connection, but failed using OLEDB connection, with the same account, password and all.

Has anybody met this situation?

There's no error message, and the stored procedure did run for a while.

The only problem is that there's no data return.

Can anybody help to explain and solve it?

Thank you in advance.

Best regards,

Patrick

[#2]

Hi all,

I've found the cause.

It's because when using OLEDB, the stored procedure must include "set nocount on" statement.

FYI.

[#3]

Thanks! This worked for me as well and corrected the issue. QV needs to fix ASAP. Thanks again for the help!!