Sinc e you have given no info on what is the problem, you will not get much help. Having supported a couple of apps that used access, my guess is that you are pulling every row from a table into access, with no restricting where clause to limit the data. So, as your table gets bigger it will take longer to put that data into access. Also, I don't know what the limit on nbr of rows is in access any longer, but you could reach that at some point in the near future. Indexes may help if there is an actual where clause being executed. You could run the query through design adviser to see if there are any suggestions on that front. Then there's always have you done any maintenance work such as reorgs/runstats. etc... there is tons of data in the archives here on improving performance and thru put as well as the IBM redbooks and google is very useful for finding help. You may want to read through some stuff prior to the next query.
Dave