Hi everybody,
I have an access database which is around 40 MB after compacting it and I feel that it is slow especially when I open cross table form. Is there any way to speedup the databse.
Note: my databse is on the share drive in my work.
I recall reading somewhere (fairly recently) about a parameter or property in Access which is "On" by default and allows a form/query to identify when backend table field names or query arguments are changed and automatically looks for and "fixes" the renamed link. By leaving this switched ON, the database is slower than it could be. The db speed performance can be can be improved significantly by switching this 'feature' off. (i.e. Name of the property)
I'm having trouble with access. Basically it has been very slow to load (over 30 seconds when not opening a database) and when opening a database it just crashes.
Has anyone any idea what could cause this as it worked fine before ?
This problem is driving me nuts!! I`ve just spent a fair few months creating a database to be used by our sales team, I`ve about finished it and came to trial it with the sales manager. When he is using the database at the same time as me it becomes slow. The design has a front end with all the queries, forms etc and a back end on a server containing the tables. The database was created using Access 2000 and was designed to replace a similair db created on 97 which has a decent speed on the network. The other strange thing is that one particular macro that I`ve been using for the speed tests runs quite slow (about 3 secs) when 2 pcs have the db open but once the macro has run if it is run again it takes typically less than a second to run. What would cause a db to run a macro at different speeds after they`ve been run once? I`ve tried everything I can find on the net to try and improve the speed to no avail. Help please!!
The database response is significantly slow when our application requests data over a network. Are there any settings to adjust network response? The network is connected via a T1 line.
According to information I've found online, our application is the front end to the database and the database sits open on the server.
I have two databases, one is much larger than the other, but both have the same start up code. The larger database opens quickly, but the smaller database takes forever. I tried compacting and repairing the front end and the back end of the database, but that did not help. Any ideas on how I can speed this up?
My database is opening much slower than normal just over the past few days. When I run a performance analyzer it is telling me that my database is only being compiled in a partial state. How did this happen and what do I do to fix it??
On occasion my access database all of a sudden begins to operate very slowly, I notice the queries take a much longer time to run.
Last week it suddenly began to operate very slowly after idling in excess of 30 mins
Today when I change the screen to design view and then back to form view once again it begins to operate very slowly. (yesterday was working fine on my desktop at home, I have not made any changes to the database with exception to saving and using the file this morning on the shared drive at work) If I shut down and re open it operates well but once again changing to design view causes the same issue. Sometimes compact and repair rectifies sometimes not.
I have developed a DB for work and it has grown, it is about 60Meg, all of a sudden when I am opening Design View in Reports, or queries it started running really slow.
I always Compact on Close I have Split the DB.
Still no Joy, I have a brand new Dell PC so nothing wrong there.
What is happening? it is a nightmare to get anything done.
I've been searching for an answer for a long time, but i have a database with approx 100 forms, 100 tables (most linked to SQL Server) only a small proportion are front end tables, 50 or so queries, 20 or so modules.
Anyway the problem is, is that the database is slow, to open and to develop in, i have a decent system to develop on with a 3GHz CPU and 1 GHz RAM, but i dont get this problem with any of the other access databases i deal with.
It's kind of a lagging effect, then once it has been written into memory it's quicker... but why would that be different between the systems, as most the systems i deal with are fairly similar in size and in complexity.
For example when loading the logon screen, which is a simple unbound form, it seems to lag, there is 1 combo box which has a front end table as its row source, like 6 records. Then a username and password text boxes which are not bound to anything. Why should this be lagging? After like 2/3 secs its then ok, once ive logged in and then go back to this logon screen its fine, so i think it has something to do with memory.
Anyone else had anything similar happen to them and did they do anything to minimise this lagging effect?
My acccess (.mde) application suddenly slowed down. I have increased the size for some fields in some Tables. Is it could be the reason for this? Is there any way i can get the speed back.
I not a big time DB person so please be gentle. I am a computer technician at a school district and need some help. We use a program called Aeries made by Eagle Software for out attendance and grading. It uses an interface that runs through Microsoft Access. There are two version of this software. One is the SQL version and the other just uses an Access DB on a server. We have the Access DB version running Access 2003. It was explained and accepted in the beginning that we didn’t really need the SQL version because of our district size which is some where around 1500 students. Our district consists of 6 school sites that are all connected with a fiber optic backbone running at 200mb with a minimum of 100mb to each desktop. We have a DB for each site running on 1 very beefy server in a central location. I’ve run my problem by the software maker and don’t feel like I’m getting much help. The problem I am having is slowness during login. When the first user of the day attempts to login the program is fast, about 10 seconds from “ENTER” to the main menu. As soon as that 1st user clicks one of the menu buttons anyone else who attempts to login to that database after that experiences at least 30 seconds from “ENTER” to the main menu. I’ve watched what files are accessed and when. I see that when the 1st user logs in, the systemxp.mdw file is accessed and a systemxp.ldb file is created. Then when the user clicks a button on the main menu, the sch05xxx.mdb is accessed and a sch05xxx.ldb file is created. The sch05xxx.mdb file is the main database file for any particular site. The “xxx” would be the site number. As soon as that file is accessed or that lock file is created the user will experience the long login times and sometimes as long as 4 minutes. I don’t believe this is a hardware problem. During the same time that users are slow I have made a copy of one of the databases onto the same HDD on the same server and as long as I’m the 1st person to open it, it will fly. The 2nd person is slow just like the rest. I also don’t think it’s a permission issue, at least not in the domain. I’ve run all these test logged in as myself and have Domain Admin rights to everything. I believe this is a “split database” with the tables on the server and the forms, and queries on the users computer. I read an article here, http://www.microsoft.com/office/previous/xp/columns/column05.asp called “Why is Access 2000 slow for more than one user?” Has anyone else had this problem or have a solution? If I’ve missed something and you need more info please let me know.Thank you for your time and I appreciate any responsesJohn
I have access 2003 installed on two different machines. One machine was built 6 months ago with the best hardware available. The other was an older slow IBM.
For some reason, I am experiencing what appears to be some serious time delay (talking in the range of seconds, sometimes tens of seconds) when building a report that has a subreport in it on the fast machine. Yet when I load the exact same database on the slow machine, the report opens instantly.
I have an access database that runs fine on our current systems (mix of office 2002, 2003 and windows xp/2002.
However we have one new machine here running windows vista and office 2007 and the database runs super super slow. just about every operation takes 10 times plus to run!
I have looked at the sticky subject at the top of this forum and it's not the problem linked to here http://support.microsoft.com/kb/935366/ as this uis the only vista machine we have accessing the database. the same problem also occurs when running locally on my home machine (again vista and office 2007). From memory if is fine when running it through office 2003 on vista.
Anyone else have similar problems and find a solution?
Any ideas why a particular query would run very slow in access 2007 when it runs fine on 2003. This is running on a terminal services environment and the database connects to a ms sql 2000 server. I will try it outside terminal services when I can but I can't understand the problem. Im not talking about slightly slower its something like a factor of 100 or 200 slower (I had to limit the dataset just to get a return within a day).
The database was an access 2000 mdb for compatibility across computers but I have tried converting it with out any luck.
I am using MS Access 2000 in a Windows Terminal Server 2003 Environment and the performance is incredibly slower than running the same job on a Stand Alone CPU with Access 2003.
Any idea? Access 2000 is running slower on a TServer? May the Access version difference explain the difference?
Is Access slower at summing null records than SQL server? I have a query which takes less than 1second in SQL server but takes about 5-10 in Access but can't think why there is such a lag in processing speeds.
I have completed a database for a company with 60 000 clients and over 100 000 job records.
The database works at very resonable speeds on the Server computer, or the computer on which I installed the back end of the database.
Each of the other 3 computers on the wireless network, have a local copy of the Front End on their machine, and reference the Back End (BE) on the server computer.
Each of the Client computers have varing speeds when accessing the BE, some as slow as 10 minutes for a simple search, filter or just loading a form.
What can I do to improve performance across the network?
Do I need to install additional components on the other computers to improve the db performance?
I am using John Big Bootys Dynamic Search Form (built in Access 2003) as it totally met my search requirements, however when typing anything into the search box it is realy slow, taking several seconds for each letter to show in the box.
This has always been a problem now and again, however some of us have upgraded to Office 2010, (although still using the 2003 built Db as we won't move to a 2010 version Db untill March next year) and now the problem is even worse that ever. Everything else seems to work really well except for this search function, however it is the search function that is used more that anything else.
My DB is very slow when it's used by more than 1 person at a time. It's divided into FE/BE. The BE is in a shared server and a copy of the FE is in each person's machine.
I don't know why it takes ages to respond. Any help will be very much appreciated.
I have an Access 2003 db that works extremely well as a stand-alone application but I am keen to “split” it so that many users can operate it together.
Accordingly I did the split and placed the tables on our server, and tried running the front end locally.
Much to my horror, it takes about a minute to open, and many seconds to do anything after a button press etc.
I have been testing it on my wireless home network and the same thing happens, except now I can monitor network activity from the “network working” light.
What I see baffles me and would welcome comments, in particular, what I can do to speed it up by a factor of 100!
1.It takes forms about 50 seconds to open; however, this is due to about 40 seconds of network activity BEFORE the form’s load event fires! 2.In DESIGN mode, any minor change to a control for example, results in about 40 seconds network activity. 3.All queries upon which forms are based take well under a second to run over the network. 4.Making an mde file has no effect.
I thought the idea of splitting was to keep the forms/queries/code etc, local to a machine so I don’t understand what all the network activity is about, particularly in design mode. Also, given the actual queries are so fast, just what is Access doing??
I have a form with a subform (there is no child parent relationship) , when I open the mainform it causes the subform to slow down.
ie If I open the suform by itself - it opens quickly If I then open the main - it runs quickly
If I then open the main again it runs slow or if I open the subform again - it runs slow - it continues to run slow - until I have opened the sunform by itself.
So something in the mainform is causing the subform to slow down.
i'm create a aplication in ms access 2000 developer edition. this app comunicate with sql 2000.
we have problem with slow connection provided by access. in headquater wher people use access app it working quickly. sql 2000 is localted at headquarter too. but if i run app in warehouse it working very slowly.
VPN connection doesn't slow. but access can't use all vpn connection capacity but only 1/5 from this capacity?
how can i do something that acces can use all capacity that i have?
example: link is 512 kbps but access use only 100kbps and work very slowly.