baffled100
Technical User
Hi,
I have an Access 2003 database that has started misbehaving somewhat suddenly. The actual database works fine when on my local system, but across the network, it is very slow to open a particular form based on a table of about 24000 records. I have a combo box to look up people in the table that uses a filter on the table and that is slow also for the first person you are searching for. Subsequent searches are faster. It's as if once the table has been opened, the speed improves.
Other details......compact and repair takes at least 4 times longer than usual. The error message "You can't carry out this action at the present time" periodically will pop up, but not necessarily at the same places in the program. The 'Not Responding' program message appears more often.
I rebooted the server yesterday and it seemed to improve for a day, but it is back to being slow again. I checked to see if there has been any Office updates installed prior to this behavior and there has not been. I did install some Windows Server 2008 updates on Monday night and rebooted the server, but this problem started on Thursday....
This seems to be strictly related to opening a large table over the network for the first time. The rest of the database, ie menus, reports etc open fine.
And I have copies of the same database from prior to this behavior on the live database and they too behave the same way--slow. So I don't think it is a problem with the database itself per se.
This database is not split although I will be splitting it soon. But again, it was working fine without being split up until last week. I had not made any changes to anything in the database prior to it being slow.
The network does not seem to be slow for other uses.
Does anyone have any ideas? I'm fresh out....
Thanks!
I have an Access 2003 database that has started misbehaving somewhat suddenly. The actual database works fine when on my local system, but across the network, it is very slow to open a particular form based on a table of about 24000 records. I have a combo box to look up people in the table that uses a filter on the table and that is slow also for the first person you are searching for. Subsequent searches are faster. It's as if once the table has been opened, the speed improves.
Other details......compact and repair takes at least 4 times longer than usual. The error message "You can't carry out this action at the present time" periodically will pop up, but not necessarily at the same places in the program. The 'Not Responding' program message appears more often.
I rebooted the server yesterday and it seemed to improve for a day, but it is back to being slow again. I checked to see if there has been any Office updates installed prior to this behavior and there has not been. I did install some Windows Server 2008 updates on Monday night and rebooted the server, but this problem started on Thursday....
This seems to be strictly related to opening a large table over the network for the first time. The rest of the database, ie menus, reports etc open fine.
And I have copies of the same database from prior to this behavior on the live database and they too behave the same way--slow. So I don't think it is a problem with the database itself per se.
This database is not split although I will be splitting it soon. But again, it was working fine without being split up until last week. I had not made any changes to anything in the database prior to it being slow.
The network does not seem to be slow for other uses.
Does anyone have any ideas? I'm fresh out....
Thanks!