MS Access back end is located on a slow network drive

Question

I currently have an Access 2003 application that is used primarialy by three people. It is divided into a front end, each of which has a copy on its machine and a back on the server. When a user enters the interface, the front end launches a startup procedure that checks for links to tables, version number, and several other things. The problem is that the shared drive is slow, very slow. It may take more than a minute to complete the procedure.

I tested it on another network that I know faster. It took about 10 seconds to complete the same tasks. Unfortunately, I have no choice on which network the application can be hosted, so that people who need to use it can use it. Does anyone have any suggestions as to what I can do at the end to speed things up? It seems like this is more of a network problem than a problem with my design, but my chances of getting help from our IT department are null.

Answer 1

The first thing to do is to open the database variable for the backend. This blocks the opening of the LDB backend file, so Access does not waste time working on it. You can also open a record set variable.

, , , . , , .

" " .