This content has been marked as final. Show 5 replies
I have to ask the obvious, have you checked the obvious? Have you checked to see how much room you have left on the drive(s) that the db resides on? How much ram is free?
Yes that is all fine. I did however do the following to resolve the problem. in CFMX 7 Administrator under Server Settings there is a menu for Caching, I just flushed the cache. That summarily has resolved the issue. But that doesnt seem to be an answer for me. There must be some tangible reasoning behind why this has occurred.
I do agree with this http://support.microsoft.com/kb/165041/en-us here. I have done this before and amended my registry settings. I have done this last year on the same server that is gave me this issue today. But this time I flushed the Cache in CFMX 7 which sorted it out. Is there a logical explanation as to why it worked as opposed to updating the registry?
I might sound pedantic about this but just looking for answers. :)
I totally understand your wish to get to the bottom of this! There are a lot of factors that can be contributing to the problem - the query itself, the number of users hitting the query, and the tmp files internal to Access.
Make sure your query isn't returning very large recordsets (e.g. all sales for all salespersons for all year.....). Even a query with a moderate recordset return , hit by a large number of users, can cause this sort of problem.
If you must use Access in production (which is NOT recommended) your datasource settings should include:
Maintain connections across client requests be unchecked.
Limit Connections be checked and Restrict connections to be set to 1
These settings should help prevent performance issues.