When you open or are using a Microsoft Office Access database on a computer that is running Windows Vista, you may encounter one or more of the following issues:
| Access appears to stop responding. |
| Access responds very slowly. |
| Access exits unexpectedly or crashes. |
| An event that resembles the following is logged in the Application log:
Log Name: Application
Source: Application Hang
Logged: Date_and_Time
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: Computer_Name
Description: The program MSACCESS.EXE version Version_Number stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: Process_ID Start Time: Hexadecimal_Time Termination Time: Hexadecimal_Time |
After you encounter one or more of these issues, you receive the following error message the next time that you open the database:
The document Database_Name caused a serious error the last time it was opened. Would you like to continue opening it?
When you open the database, you encounter the following issues:
| All data in tables and queries shows as "#Name?"
|
| You no longer see any objects in the navigation pane. |
This problem may occur if the following conditions are true:
| The database that you are using is a shared database that resides on a Windows Vista-based computer. |
| Two or more Windows Vista-based computers are trying to use the database at the same time. |
Note If you run the beta versions of Windows Server Code Name "Longhorn," you may also experience this problem.
This problem is related to issues with Server Message Block (SMB) 2.0 when SMB 2.0 is running on a Windows Vista-based computer.
To resolve this problem, apply the hotfix that is described in Microsoft Knowledge Base article 935366.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
You can temporarily work around this problem by sharing the database from a computer that is not running Windows Vista or a beta version of Windows Server "Longhorn." We do not recommend this method as a permanent solution. You should check this article periodically for a permanent solution. Alternatively, you should contact Microsoft Customer Support Services. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about SMB 2.0, visit the following Microsoft Web site, and then see the "Server Message Block 2.0" section:
