By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,573 Members | 3,017 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,573 IT Pros & Developers. It's quick & easy.

Access Database Running slow/ODBC failed call

P: 1
Our company has an access front end database that is used by 30+ people all day, five days a week. The issues that we are running into include the database running extremely slow, not responding, and displaying ODBC failed call errors messages. We have the tables housed on the SQL server wich we thought permit nurmerous users to access the data at once. But this is not working. We are having issues with a single user with 9+ connections, or connections not closing out when a user has exited the database.

Is there anything that I can do to improve the database to prevent these things from occuring?

Feb 28 '07 #1
Share this Question
Share on Google+
1 Reply

Expert Mod 10K+
P: 14,534
Hi Octoryia

1. Are you using one front end or multiple copies of a frontend?
2. When frontend(s) is closed is there still an *.ldb file left in the folder?
3. Go to Tools - options and under the General tab make sure the Compact On Close option is ticked. However, this will only work properly if there are multiple copies of the front end as with multiple users of one copy there can only be one user on for this to work. Otherwise it just creates a copy of the compacted database without compacting the original.

Feb 28 '07 #2

Post your reply

Sign in to post your reply or Sign up for a free account.