http://support.microsoft.com/?kbid=935370
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.
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.
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.
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.