Date Filter slow to Load Access 2010
I have an Access application running in Access 2010 on Windows 7.
When I right click on a date field and click on "date filters" to pull up the sub menu there is a delay that lasts several minutes. If I leave it until it comes up then it will display the next time as expected.
It is not the filtering that is taking a long time, its loading the menu that takes forever.
Any thoughts?
When I right click on a date field and click on "date filters" to pull up the sub menu there is a delay that lasts several minutes. If I leave it until it comes up then it will display the next time as expected.
It is not the filtering that is taking a long time, its loading the menu that takes forever.
Any thoughts?
Can you post the database so we can look at it?
ASKER
Helen
Not sure exactly what you are asking for but if you want the COMPLETE database then no, this table alone contains several million records.
What exactly are you looking for?
Not sure exactly what you are asking for but if you want the COMPLETE database then no, this table alone contains several million records.
What exactly are you looking for?
Run the Performance Analyzer?
You may need an Index for the Date field in the table. Since it runs faster after the first run.
You may need an Index for the Date field in the table. Since it runs faster after the first run.
ASKER
It already has an index that is rebuilt nightly. This issue is loading the.menu. not retrieving the data
ASKER
DoDahD - As a check, I rebuilt all indexes this weekend and the problem still exists.
Additional info: The problem first raised its ugly head on my system. I am running Office 2010 Professional Plus with SP1. I tried it on another machine that does not have SP1 and the problem is not near as bad. Something that should pop up right away takes about 3 to 4 seconds without the Service Pak and about 5 minutes with the service pak.
Additional info: The problem first raised its ugly head on my system. I am running Office 2010 Professional Plus with SP1. I tried it on another machine that does not have SP1 and the problem is not near as bad. Something that should pop up right away takes about 3 to 4 seconds without the Service Pak and about 5 minutes with the service pak.
ASKER
More information:
I have Office 2010 Professional with service pack 1 loaded. On a system that does not have SP1 loaded this issue is not as bad. None SP1 - takes about 4 or 5 seconds, with SP1 5 minutes. Seems like anohter SP1 problem.
Even more information:
This form is tied to a query that uses a customer ID to select the records. (Select * from [table name] where [customer id] = 'XYZ'). The Customer ID is indexed and so is the date field I am trying to work with. All indexes have been rebuilt.
The SP1 5 minute result happens with a customer that has 490,000 (+-) rows. I did the same test on a customer that has 39,000 (+-) rows and the delay is substantially shorter (about 15 seconds) but still not acceptable.
It looks like Access is querying the database to determine what options should be displayed in the pop up menu.
This is a critical issue.
I have Office 2010 Professional with service pack 1 loaded. On a system that does not have SP1 loaded this issue is not as bad. None SP1 - takes about 4 or 5 seconds, with SP1 5 minutes. Seems like anohter SP1 problem.
Even more information:
This form is tied to a query that uses a customer ID to select the records. (Select * from [table name] where [customer id] = 'XYZ'). The Customer ID is indexed and so is the date field I am trying to work with. All indexes have been rebuilt.
The SP1 5 minute result happens with a customer that has 490,000 (+-) rows. I did the same test on a customer that has 39,000 (+-) rows and the delay is substantially shorter (about 15 seconds) but still not acceptable.
It looks like Access is querying the database to determine what options should be displayed in the pop up menu.
This is a critical issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
MSFT issued an update that fixed the problem.
ASKER