G
Guest
We are experiencing a weird problem where a call to a stored proc using
native SqlClient connection class in a VB.Net app fails on one machine when
processing a large set of data (23,000 rows) BUT will always work on another
PC. We checked patching and both are (now) running SQL Server SP3a and also
the version of MDACs is 2.7 SP1 refresh. The other DLL's we use DTS and EXCEL
are deployed with the app. Small sets of data run fine on ALL machines all of
the time. The stored proc runs successfully when executed from SQL Query
Analyzer.
Has anyone experienced anything like this? Here's hoping! I'm running out of
ideas of things to check. Trying to trap the error returned a blank string?
Thanks
native SqlClient connection class in a VB.Net app fails on one machine when
processing a large set of data (23,000 rows) BUT will always work on another
PC. We checked patching and both are (now) running SQL Server SP3a and also
the version of MDACs is 2.7 SP1 refresh. The other DLL's we use DTS and EXCEL
are deployed with the app. Small sets of data run fine on ALL machines all of
the time. The stored proc runs successfully when executed from SQL Query
Analyzer.
Has anyone experienced anything like this? Here's hoping! I'm running out of
ideas of things to check. Trying to trap the error returned a blank string?
Thanks