William
Wed Feb 04 18:49:56 CST 2004
This is a multi-part message in MIME format.
------=_NextPart_000_0017_01C3EB3E.EB551FB0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
I suspect that your VB6 program used fewer connections because
a.. The queries ran fast enough in VB6 to release the connections to =
the pool before another was needed. Since ADOc running in ADO.NET can be =
slower (all interfaces have to be made via COM interop), they might not =
be getting done in time.
b.. The version of MDAC you're using is different and handles =
connections differently. Remember that ADOc automatically opens more =
connections in some cases when it finds the connection is busy--other =
versions do not--they throw the aforementioned exception.
hth
--=20
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.=20
This posting is provided "AS IS" with no warranties, and confers no =
rights.
__________________________________
"Lee Schipper" <las@nospamlabapps.com> wrote in message =
news:BUeUb.7561$ow4.1674@twister.socal.rr.com...
> After migrating an existing app from VB6 to VB .Net, SQL operations =
on ADO
> started giving this error periodically:
> Connection is busy with results for another command
>=20
> I am still using the ADODB library -- I did not migrate to ADO.Net
>=20
> Looking at the SQL Server enterprise manager, I see that the .NET =
version
> opens 4 database connections, while the VB6 version only opens one =
(both
> programs were tested on the same computer with the same databases.)
>=20
> Anyone have insights on why ADODB would launch multiple connections =
which
> then collide with one another?
>=20
> Thanks,
> Lee
>=20
>
------=_NextPart_000_0017_01C3EB3E.EB551FB0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=3D2>I suspect that your VB6 program used fewer =
connections=20
because</FONT></DIV>
<UL>
<LI><FONT size=3D2>The queries ran fast enough in VB6 to release =
the=20
connections to the pool before another was needed. Since ADOc running =
in=20
ADO.NET can be slower (all interfaces have to be made via COM =
interop), they=20
might not be getting done in time.</FONT></LI>
<LI><FONT size=3D2>The version of MDAC you're using is different and =
handles=20
connections differently. Remember that ADOc automatically opens more=20
connections in some cases when it finds the connection is busy--other =
versions=20
do not--they throw the aforementioned exception.</FONT></LI></UL>
<DIV><FONT size=3D2>hth</FONT></DIV>
<DIV><BR><FONT size=3D2>-- =
<BR>____________________________________<BR>William=20
(Bill) Vaughn<BR>Author, Mentor, Consultant<BR>Microsoft =
MVP<BR></FONT><A=20
href=3D"
http://www.betav.com"><FONT =
size=3D2>www.betav.com</FONT></A><BR><FONT=20
size=3D2>Please reply only to the newsgroup so that others can benefit. =
<BR>This=20
posting is provided "AS IS" with no warranties, and confers no=20
rights.<BR>__________________________________<BR></DIV></FONT>
<DIV><FONT size=3D2>"Lee Schipper" <</FONT><A=20
href=3D"mailto:las@nospamlabapps.com"><FONT=20
size=3D2>las@nospamlabapps.com</FONT></A><FONT size=3D2>> wrote in =
message=20
</FONT><A href=3D"news:BUeUb.7561$ow4.1674@twister.socal.rr.com"><FONT=20
size=3D2>news:BUeUb.7561$ow4.1674@twister.socal.rr.com</FONT></A><FONT=20
size=3D2>...</FONT></DIV><FONT size=3D2>> After migrating an existing =
app from=20
VB6 to VB .Net, SQL operations on ADO<BR>> started giving this =
error=20
periodically:<BR>> Connection is busy with results =
for=20
another command<BR>> <BR>> I am still using the ADODB library -- I =
did not=20
migrate to ADO.Net<BR>> <BR>> Looking at the SQL Server enterprise =
manager, I see that the .NET version<BR>> opens 4 database =
connections, while=20
the VB6 version only opens one (both<BR>> programs were tested on the =
same=20
computer with the same databases.)<BR>> <BR>> Anyone have insights =
on why=20
ADODB would launch multiple connections which<BR>> then collide with =
one=20
another?<BR>> <BR>> Thanks,<BR>>=20
Lee<BR>> <BR>>=20
</FONT></BODY></HTML>
------=_NextPart_000_0017_01C3EB3E.EB551FB0--