<div>
I have a access application with tables etc... that i want to make sure don't get messed up. &nbsp;I did think i might just have them copy it out to a network drive somewhere periodically.
</div>


I have a access application with tables etc... that i want to make sure don't get messed up.  I did think i might just have them copy it out to a network drive somewhere periodically.

<div>
Your &quot;access application&quot; should be split into Front-End (FE) (Forms, reports, queries, code modules, and maybe a few tables used for data in drop-downs, which almost never change) and a Back-End (BE). &nbsp;The BE (if being shared among multiple users) should already be on a network server.<br />
<br />
This configuration makes it easier to backup the FE and BE separately.<br />
<br />
Dale
</div>


Your "access application" should be split into Front-End (FE) (Forms, reports, queries, code modules, and maybe a few tables used for data in drop-downs, which almost never change) and a Back-End (BE).  The BE (if being shared among multiple users) should already be on a network server.

This configuration makes it easier to backup the FE and BE separately.

Dale

<div>
<div class="content wysiwyg-content">
Is there a best practice for backing up a Access database project?
</div>
</div>


Is there a best practice for backing up a Access database project?

backing up a access database project

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.