Article ID: 180221
Article Last Modified on 3/16/2005
APPLIES TO
- Microsoft Transaction Services 1.0
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q180221
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.
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.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
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.
Keywords: kbbug kbdatabase kbpending KB180221
