This is a discussion on SQL server driver problem within the MS SQL ODBC forums, part of the Microsoft SQL Server category; --> Hello everybody, I have stored procedure(vb6,sql server 2000(3))., that I call from VB using odbc drivers. This stored procedure ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello everybody, I have stored procedure(vb6,sql server 2000(3))., that I call from VB using odbc drivers. This stored procedure has 10 queries and it runs without problem until 4th query and then it exits without any reason and without errors. I do not see any erros in sql server profiler either. VB does not give any errors either. SP does not have output parameters and no return parameter explicitly defined in VB. Now if I change definition of the stored procedure (still using ODBC driver) if I add return parameter OR if I add output parameter (to the sp and to vb), the stored procedure will be executed until end Also if I change ODBC driver to OLEDB driver, the sp will be executed until end in any case (without any output or return parameter defined) Can somebody explain this behaviour please Thanks Diana M |