Sorry for the vague title. I wasn't sure how to word it.
I'm sort of an intermediate novice in Access, so bare with me. I have a form that when someone enters various dates and hits run (event procedure), it pulls in information based off of our clients. It runs incredibly slow due to the amount of data it must pull, and I know adding a primary key will increase the speed.
However, the queries used are select queries, and there are a few of them (one based off of the other). I change them to make table queries, and adjust the macro, but now the final product is based off of the first set of data used.
So for example, let's say I have 3 clients, Coke, Pepsi, and Snapple. The form allows all three to run, one after the other. With the make table queries as they are (using index tables to add primary keys), when I want to see Coke data, it runs fine. However, when the form pulls data for Pepsi, it gives me Coke data. Similar with Snapple.
This is because the tables that are created are frozen...so obviously, it'll give me Coke data (since it ran first). Is there anyway to have these make table queries refreshed each time a new client is about to run? Better yet, is there a way of making things go faster without having to run make table queries?
Sorry for the confusion if any. It's kind of hard to explain.