title: Performance degredation after splitting an Access DB
body: <p>We've got an Access Database Application. (Disclaimer: We'd have preferred a different technology, but things happen ...). In order to use and develop the database in parallel, we've split the DB into a "data" (backend) and "application" part as seems to be best practice for Access DBs.</p>
  
  <p>Now the performance has been degraded, queries that used to be instantaneoulsy now take a couple of seconds. This was a bit surprising, since "better performance" was supposed to b one of the pros for splitting the DB. What can we do to get performance back to the original level or even better? </p>
  
  <hr>
  
  <p>UPDATE</p>
  
  <p>We've done some more testing to figure this out. It seems to be that the problems are caused by the workgroup file (.mdw) that is accessed permanently and causes quite some network traffic (with the unavoidable latency issues). When I copy the .mdw to a local file and use that instead, the performance is great. Obviously, copying the file is not a good solution (as we want to make the Access DB available on the network to an unknown number of users). Any better ideas?</p>