>-----Original Message-----
>hi,
>
>I have a application that has many stored procedure=20
running
>fine on a Win 2000 sp3 / SQL 7 sp3 server.
>
>Recently i created a new proc. and when i run it the=20
>system always abort the execution and shows the message:
>
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]
>ConnectionRead (WrapperRead()).
>Server: Msg 11, Level 16, State 1, Line 0
>
>
>This proc. inserts records on a table and i noticed that=20
>each time i run it the proc stops after inserting a=20
>different number of rows. Sometimes just after 30 records=20
>(when running on the Query analyser, and sometimes after=20
>270 records when running on the MICROSOFT development=20
>Environment 2002.
>
>When i get the same stored procedure restore it on a=20
>different server and run it the system completes the=20
>execution with no problem.
>
>Is there any way to identify why the same proc. that runs=20
>on a server does not run in other server and aborts with=20
>the message mentioned above?
>
>Thanks a lot for your support
>
>Jos=E9 Rocco
>.
>Check your ODBC Data Source to see if you have SQL Server=20

>-----Original Message-----
>
>>-----Original Message-----
>>hi,
>>
>>I have a application that has many stored procedure=20
>running
>>fine on a Win 2000 sp3 / SQL 7 sp3 server.
>>
>>Recently i created a new proc. and when i run it the=20
>>system always abort the execution and shows the message:
>>
>>[Microsoft][ODBC SQL Server Driver][DBNETLIB]
>>ConnectionRead (WrapperRead()).
>>Server: Msg 11, Level 16, State 1, Line 0
>>
>>
>>This proc. inserts records on a table and i noticed that=20
>>each time i run it the proc stops after inserting a=20
>>different number of rows. Sometimes just after 30=20
records=20
>>(when running on the Query analyser, and sometimes after=20
>>270 records when running on the MICROSOFT development=20
>>Environment 2002.
>>
>>When i get the same stored procedure restore it on a=20
>>different server and run it the system completes the=20
>>execution with no problem.
>>
>>Is there any way to identify why the same proc. that=20
runs=20
>>on a server does not run in other server and aborts with=20
>>the message mentioned above?
>>
>>Thanks a lot for your support
>>
>>Jos=E9 Rocco
>>.
>>Check your ODBC Data Source to see if you have SQL=20
Server=20
>2000. If not you will need to update the mdac to 2.7 it=20
>can be found in=20
>http://www.microsoft.com/downloads/search.aspx?
>displaylang=3Den
>.