title: Setting up an MS-Access DB for multi-user access
body: <p>We're thinking of "growing" a little MS-Access DB with a few tables, forms and queries for multiple users. (Using a different back-end is another, but more long-term option that is unfortunately currently not acceptable.)<br>
  Most users will be read-only, but there will be a few (currently one or two) users that have to be able to do changes (while the read-only users are also using the DB). We're not so much concerned about the security aspects, but more about some of the following issues:</p>
  
  <ul>
  <li>How can we make sure that the write-user can make changes to the table data while other users use the data? Do the read-users put locks on tables? Does the write-user have to put locks on the table? Does Access do this for us or do we have to explicitly code this?</li>
  <li>Are there any common problems with "MS Access transactions" that we should be aware of?</li>
  <li>Can we work on forms, queries etc. while they are being used? How can we "program" without being in the way of the users?</li>
  <li>Which settings in MS Access have an influence on how things are handled?</li>
  <li>Our background is mostly in Oracle, where is Access different in handling multiple users? Is there such thing as "isolation levels" in Access?</li>
  </ul>
  
  <p>Any tips or pointers to helpful articles would be greatly appreciated.</p>