I have a database where the back end is located in a network folder and each user has a copy of the front end. This includes the main table (which is very small - less than 200 entries), a ZIP code latitude and longitude table (obviously very large), and a couple of lists that I use for combo boxes. Other than the main table, the other tables will most likely never be updated.
According to the users (which are spread out around the country), it is running very slowly on both open and ZIP code distance searches. They say it takes around a minute just to open the file whereas mine opens in less than 10 seconds.
My question is this - Would it be appropriate, since the large ZIP code table and the list tables never need to be updated or changed, to include these tables in the front end to speed things up? If not, what are some other ways that I can optimize this? I have never posted a database to a network folder before, and since I am having no problems with the version that is on my computer (even though it is still pulling the linked tables from the same network location), I am having a hard time understanding what to do next. I have done quite a lot of research and tried several suggestions (compacting and repairing both FE and BE, using network address instead of drive address, optimizing code, etc.) Thanks for any help you can give.