Also, if you create a new ODBC data source with the MDAC 2.1 or later version of the Access ODBC Driver, the driver incorrectly uses a default value of 5 for PageTimeout. The correct default value should be 5000 with the MDAC 2.1 version of the driver.
You can also add this to your ODBC connection string. For example, here is an ODBC connection string that uses a DSN as well as adds the PageTimeout setting:
"Driver=Microsoft Access Driver (*.mdb);PageTimeout=5000;DBQ=C:\MyFile.doc;"
To determine which version of the driver you have, start the ODBC Administrator tool and click the Drivers tab. If the version of the Microsoft Access ODBC driver starts with 3, you have an MDAC 2.0 version of the driver. If the version starts with 4, it is an MDAC 2.1 or later version of the Microsoft Access ODBC driver.
To reproduce this issue, you need a network packet monitoring tool such as Windows NT Network Monitor as well as the ODBC Test tool that is installed by the Microsoft Data Access SDK 2.1. Note that any ODBC client tool that can open an ODBC connection and leave it open can be used in place of ODBC Test.
Drivers required for Network Monitor are included in all versions of Windows NT and Windows 2000. The Network Monitor application required for monitoring traffic is included only in the server versions. For more information on Network Monitor look in the Help included with the operating system and MSDN.
Steps to Reproduce Behavior
- On the client computer, create a new ODBC Data Source (DSN) named
TestPageTimeout that uses an Access database that resides on another computer on the network.
- On the ODBC Microsoft Access Setup dialog of the new DSN,click Advanced to confirm that the PageTimeout setting has a value of 5.
- Start ODBC Test then Click Connection and select Full Connect.
- Select the TestPageTimeout data source created in step 1 and click OK.
- To activate the PageTimeout related packet activity, open the remote database file using another client and make a change to the database. For example, opening the remote database in Microsoft Access and modifying any record in any table suffices.
- Wait about 60 seconds and begin monitoring network packet activity between the client and server computers. Note that even though the ODBC connection opened by ODBC Test is idle, a large amount of continuous packet activity between the client and server is generated.
ID d'article : 246560 - Dernière mise à jour : 4 août 2008 - Révision : 1