Download to Access
OK now it becomes clear. I have experienced what you are going through.
Firstly, I had two Access databases, template and live. Template was a empty table structure, no indices on the tables but a set of queries and macros to generate the indices.
The starting process was for a batch file to copy template over live. The reason being that Access database grow and grow with use and there was no way to compact the database from within SQL.
Secondly Access doesn't mind multiple connections that read its database but it hates multiple connections that write. This doesn't always manifest itself but believe me it is true.
The standard SQL Server DTS wizard to download to an access database will generate multiple connections for SQL Server and Access. Go through the DTS package and make sure there is one connection each.
My experience was that run locally the original SQL to Access transfer would run like a rocket. Run remotely sometimes it would work, sometimes it would run dog slow, other times it would simply freeze solid.
Taking the steps that I have described here means that, whilst not being as fast as the default with all things working fine, it was at least reliable.
All the user had to do once the database was produced was run a single Macro that ran all the queries that add indices to the access tables.