Microsoft Knowledge Base Email Alertz

(202376) - Applications that use the Microsoft Jet Database Engine can prevent a computer that supports the Advanced Power Management (APM) or the Advanced Configuration and Power Interface (ACPI) technologies from going into Standby mode.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 202376 - Last Review: December 5, 2003 - Revision: 4.1

PRB: Idle Jet Application Can Prevent Standby Mode

This article was previously published under Q202376

SYMPTOMS

Applications that use the Microsoft Jet Database Engine can prevent a computer that supports the Advanced Power Management (APM) or the Advanced Configuration and Power Interface (ACPI) technologies from going into Standby mode.

CAUSE

If the application opens a database in shared mode using one of the Jet drivers with the default settings, the Microsoft Jet Database Engine reads from the database file every five seconds (or 5 milliseconds, depending on your PageTimeout settings). The resulting hard drive activity prevents the Standby mode from activating.

RESOLUTION

Either open the Jet database file in exclusive mode or close all database connections when your Microsoft Jet Engine using the application is idle.

STATUS

This behavior is by design.

MORE INFORMATION

The Microsoft Jet Database Engine invokes a background thread which monitors every database opened in non-exclusive (shared) mode. The Jet Engine uses a configuration setting called PageTimeout. PageTimeout determines when this background thread should check the database file for new updates. By default, PageTimeout is set to 5000, which is 5000 milliseconds or 5 seconds. (Note that in the recent versions of Jet 4.0 this number is set to 5 milliseconds by default.) So when using the default settings in multi-user access mode, every five seconds Jet reads a small amount of data from the database to check to see if anything has changed. You cannot turn off the PageTimeout feature when using a database in multi-user (shared) mode.

If you open a database exclusively, the background thread no longer needs to monitor the database file periodically. Opening a database exclusively improves performance, this is a desired mode if your application does not share the database with other clients.

APPLIES TO
  • Microsoft Data Access Components 2.0
  • Microsoft Data Access Components 2.1
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.6
Keywords: 
kbdatabase kbjet kbprb KB202376
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate