Very slow when linked on a shared network drive...?

[nhoff]

Hi there

I have a database, which consists of a datafile (all the tables) and a userfile (all the queries, forms, reports etc.). My datafile is located at a shared network drive and the userfile is on desktops around my organization so that many users can acces the data simultaneously.
My problem is that it runs very, very slow like this. When I open forms it sometimes takes up to 3 minutes to open them and reports are approx. 15-20 sec. in the brewing.
The datafile is not larger than approx. 1 Mb, the userfile is aprrox. 5,5 Mb.
Does anyone know anything I could try to make it work faster?
(I just getting to know VB so if a possible solution has anything to do with that, just point the direction and I'll try to walk the distance )

Thanks in advance

NHoff

 

[sparx]

The problem is probably with you network, and not with Access itself. What does you database do? And what version of Access are you currently using?

 

[Kevin_S]

nhoff -

Have a look at these links as I am betting that you are using tables as the recordsource for your forms and queries and this is causing the performance problem. Have a look at these links and also try searching on keywords like "db performance" and "form recordsource"

DB Performance:
http://www.access-programmers.co.uk...adid=47487&highlight=access+slow+over+network

Here is the search link with many other posts relevant to this topic:
http://www.access-programmers.co.uk...d=248763&sortby=lastpost&sortorder=descending

HTH,
Kevin

 

[GMLWORLDCHAMP!]

hurry up and wait...

nHoff:

Check out my response to the thread called, "DB runs slow over network"

Also, check with your office IT Administrator/Network Administrator and ask how old your network switch boxes may be and suggest upgrading to something more up to date (i.e Hawking company makes solid 24 to 48 port Network switches and hubs).

Also, check each of the PC's CAT5 patch cables; like anything in technology, things wear out, become crushed, dented, cut, etc...if this happens, it drains the resources and performance away from your network so simply replacing or even rerunning new cables can help!

Best of luck!

 

[boblarson]

Also, if your users are all connecting to a single Access database over the network, that will impact it heavily as well. You should have it split into a front-end, back-end and each user have a copy of the front-end on their pc, if possible. Also, if you have tables which are mostly static and unchanging, you can store that data as tables in the front-end and set a process by which they get updated from the backend at specific times, that will increase performance. So, for example, if you have a combo box that pulls the list of employees, if the employees list only changes when a new employee is added or an employee goes away, then create a button, or another process, to update the employees table in the front-ends only at that time. Then, the combo box will load almost immediately for your users and they won't have to wait for the system to query something in the backend.

Plus, what Kevin S. said about making sure you are only loading the things the user needs at the time they need it (not having one form with multiple combo boxes, etc. all based on a table and not on queries to limit the records being returned), is important.

 

[The_Doc_Man]

Also, if you have a switchboard or startup form that does anything with the database, even a select query, you could have a problem.

Also, remember that a network is never faster than its slowest link. So verify the number of hops between the end-user machines and the file server.