ACC2000: Objects List Takes Longer to View in Database Window

In a Microsoft Access database that contains hundreds of forms, reports, macros, or modules, you may see one or more of the following symptoms:

• In the Database window, when you try to view an Objects pane that has a large number of objects in it (for instance, 1200 forms), Access hesitates, and it may take 30 seconds to a minute for the list to appear.
  
  
• If the database has been closed and saved at an Objects pane that has a large number of objects in it, it may take as much as a minute to open the database.
  
  
• You notice that no matter which Objects pane you were viewing when you closed the database, when you open the database, it always returns to one, specific Objects pane.

NOTE: This issue does not apply to having large numbers of tables or queries. This issue applies only to the Forms, Reports, Macros, or Modules Objects pane.

This issue is related to the way Access processes information about each individual object before displaying it in the Database window. Also, because of this issue, information about changes that you make to the Database window, such as which Objects pane you were viewing when you closed the database, may not be saved.

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base: To temporarily work around this problem, try reducing the number of objects in your database by doing one of the following:

• Delete forms, reports, modules, or macros that you are no longer using.
• If possible, combine some of the objects that use the same data source or have a similar purpose. For instance, if you have three forms that have the same data source, combine them into one. Also, if you have modules that contain similar code, combine them into one module.
• Create a second database containing linked tables pointing to the first database, and then export some of the less frequently used objects to it.
  
  This would especially work if the database is used by different groups of people who do not use each other's forms or reports. Breaking the database out into separate databases that contain linked tables pointing to a centralized database is a good solution in this case.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2000 SR-1/SR-1a.