![ms access app ms access app](https://www.pcaccess.co.uk/images/link/pfbiad.jpg)
However, from what I see in list of tables, there are dozens (if not hundreds) of different tables in the original MDB file, most of them pointing to other tables within other files - all located on the network share. When a user runs an app, he actually runs an MDB file located on his HDD, and the app connects to the DB on the share. The application files are located at user's PC, while the DB is located on a server share. This is not a single, large system designed to care for all tasks - there are quite a few other applications (of them about 5 major ones) built to care for different user needs in different departments. However, this programmer made a myriad others, with about 40 user using some of them throughout the day. We are talking about 7 end-users for the particular application. Is it possible that moving the database (usually sized between 100 and 200 MBs) to SQL server would remedy the issue? The connection to the server is through 1Gbps LAN and two switches.Īny ideas why this might be happening? I cannot understand if the issue is networking, server or the Access itself? We have another, resource-gobbling SQL application in our network, which works great under similar conditions. If I copy all database to user's computer and run everything basically off user's PC, the application works fast. If I use a move the database files to a more powerful server, the app works faster, but without great difference - say, about 20 seconds. The app exhibits similar issues in other areas as well, all similar to scenario portrayed above. It takes user around - or beyond - 90 seconds to get back to the job selection screen. At this stage, the app connects to the share and writes the data to. Now, when a user is finished working, he clicks on a button taking him back to the job list. When the users clicks on a job, the application connects to a share on a server and downloads data for the particular job. It usually takes 7 to 12 seconds for the window to open (currently considered OK time). When the user clicks a job name, he is taken to a new window, where he can edit parameters of the job. We are a publishing company, thus each job contains many numbers - page sizes, name of the books and author, dimensions, colors, etc, etc. Each requests contains quite a lot of data.
#MS ACCESS APP WINDOWS#
The application exhibits slow access, with particular windows taking up to 90 seconds to change.įor example: the application shows a list of customer requests. The application is MSAccess-based, with its database also based on Access (instead of SQL). Sorry for asking a somewhat vague question, but I have no understanding of MSAccess and am being asked to resolve an issue I basically know nothing about.Ī programmer of ours created an application years ago.