Slow Performance in Jet 3.51 When Editing Recordset Generated from SELECT Statement (247613)
The information in this article applies to:
- Microsoft Data Access Components 2.0
This article was previously published under Q247613 SYMPTOMS
Performance is slow when using a Microsoft Jet Database Engine 3.51-based application and editing a recordset generated from a SELECT statement. The problem is seen when editing the first record in the recordset, although all subsequent edits of the same recordset occur within expected timeframes. The performance hit increases with the number of columns in the query.
This performance problem does not occur if the records are edited by directly opening the table (for example, when using adCmdTableDirect in ADO). There is also no performance hit if the tables were created using CREATE TABLE statements rather than CreateTableDef() statements in DAO.
This problem occurs with Jet 3.5 versions after 3.51.2723. This performance issue does not occur with Jet versions 3.50.3428.0 (Office 97 original release) and earlier, and also does not occur with any Jet 4.0 version.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Jet 3.51 Service Pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question. WORKAROUND
Create new, matching tables using CREATE TABLE statements; move your data into the new tables, and swap the names of the old and new tables.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbJET kbQFE KB247613 |
|---|
|