Occasionally the ADO object calling the stored procedure will cause SQL Server to submit the query with the SET FMTONLY ON command, and according to Microsoft this is supposed to be fixed by the MDAC 2.6 Service Pack 1.
We have been using the Service Pack 1 for a while now, so
we are left to two other options:
Use the OLEDB Provider for ODBC rather than the SQLOLEDB Provider.
--other VB components are encountering problem when using ODBC so this option is out.
-or-
Put additional transactions around the code that creates the problem.
--Tried to put an explicit transaction around the SP that
is being issued with SET FMTONLY ON by ADO didn't work.
Anyone has other suggestion?
We have been using the Service Pack 1 for a while now, so
we are left to two other options:
Use the OLEDB Provider for ODBC rather than the SQLOLEDB Provider.
--other VB components are encountering problem when using ODBC so this option is out.
-or-
Put additional transactions around the code that creates the problem.
--Tried to put an explicit transaction around the SP that
is being issued with SET FMTONLY ON by ADO didn't work.
Anyone has other suggestion?