Should I deploy a front-end MDE file instead of an MDB? What might be the benefits?
<p>Yesterday I split our database and placed the FE and BE on a shared drive for other people to access. The FE is an .accdb file but in all of my research I'm to assume that's the same as MDB?</p>

<p>I need to be able to edit the forms and queries while other users are accessing the FE. I deployed a very basic FE for them to use but now I need to make it more robust. I currently can't do that without receiving an error message about not having exclusive access. </p>

<p>So I have a couple of questions in regards to the treatment of this database now.</p>

<p>1) If I move the FE, will it still be linked to the BE? If I move the BE will that alter the file path and corrupt the links, making the FE unusable?</p>

<p>2) Are .accdb and MDB synonymous or am I well off the beaten path here? I understand that MDB is used to make edits/changes while you're meant to provide your users with an MDE version.</p>

<p>3) Is the file conversion an option within the database? Is there a tab or button on the ribbon that creates an MDE version? Are there are downsides or potential issues with 4-5 people accessing the MDE and will it remain linked to the BE if I move it?</p>

<p>4) Once I've made the desired changes to the MDB, am I supposed to overwrite the MDE or just make a new one, place it on the shared drive and point the users there?</p>

<p>Thank you all for the help. I haven't gone to school for Database Management. I was thrown into this job and I'm doing my best to stay afloat. This is all fairly new to me.</p>