Article ID: 180221 - Last Review: March 16, 2005 - Revision: 1.1

BUG: MTS Connection Pooling Problem with Visual Basic 5.0

Retired KB ArticleRetired KB Content Disclaimer
View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q180221
Expand all | Collapse all

SYMPTOMS

Microsoft Transaction Server (MTS) does not correctly pool database connections when using RDO 2.0 after installing Visual Basic 5.0 Service Pack 2. A new connection is created with each call to the database instead of using the already existing connections.
Back to the top

RESOLUTION

The two resolutions are listed below:

  • Install ODBC version 3.5.

    -or-
  • Edit your Data Source through the ODBC administrator. Find the check box 'Create temporary stored procedures for prepared SQL statements' and clear it. Use this Data Source Name (DSN) to connect to the database. Do not use a DSN-less connection.
Back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Back to the top

MORE INFORMATION

If you are using SQL Server you can use the SQL Performance Monitor (Perfmon.exe) to check your active connections. If connection pooling is not working, you will see the User Connections counter increase by one each time you activate a method that uses RDO from your MTS server application.
Back to the top
APPLIES TO
  • Microsoft Transaction Services 1.0
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition
Back to the top
Keywords: 
kbbug kbdatabase kbpending KB180221
Back to the top
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top