This is a multi-part message in MIME format.
--=_NextPart_000_0026_01C360BE.A39C7B60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
When using VB with SQL Server we get the following errors at various = times: Connection is busy with results of another command Cannot create new connection because in manual or = distributed transaction mode Is there a way to fix this problem without changing code. I am = using static cursor type while retrieving the data.
I am using Visual basic 6.0 with SQL Server 2000 and the operating = system is Win 2000 professional.
TIA,
Gary
--=_NextPart_000_0026_01C360BE.A39C7B60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
When using VB with SQL Server we get = the following errors at various times: Connection is busy with = results of another command Cannot create new connection = because in manual or distributed transaction mode Is there a way to fix = this problem without changing code. I am using static cursor type while = retrieving the data.
I am using Visual basic 6.0 with = SQL Server 2000 and the operating system is Win 2000 professional.
TIA,
Gary
--=_NextPart_000_0026_01C360BE.A39C7B60--This is a multi-part message in MIME format.
--=_NextPart_000_002A_01C360AD.DA018FD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The connection busy issue is because you haven't closed the recordset =before trying to execute another query on the same database connection =object - try setting the recordset object to nothing or use another =database connection object.
Not sure about the second - what are you doing?
-- Tony Rogerson
SQL Server MVP
http://www.sqlserverfaq.com?mbr=3D21
(Create your own groups, Forum, FAQ's and a ton more)
--=_NextPart_000_002A_01C360AD.DA018FD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
The connection busy issue is because =you haven't closed the recordset before trying to execute another query on the same =database connection object - try setting the recordset object to nothing or use =another database connection object.
Not sure about the second - what are =you doing?
-- Tony RogersonSQL Server =MVPhttp://www.sqlserverfaq.com?mbr=3D21">http://www.sqlserverfaq.com=?mbr=3D21(Create your own groups, Forum, FAQ's and a ton =more)
--=_NextPart_000_002A_01C360AD.DA018FD0--
No comments:
Post a Comment