MS Access Tools: How To Convert And Deploy An Access Database File As An Executable (ACCDE Or MDE)

MS Access Tools: How To Convert And Deploy An Access Database File As An Executable (ACCDE Or MDE)

Building your Access database for others who do not necessarily have the MS Access application or need to gain access to the design environment means wrapping and converting your file into an executable format (ACCDE or MDE). Using the MS Access tools available, this is just a start to a full deploy-able solution.

Take a look at this quick video (less than three minutes) showing first the process to convert your ACCDB/MDB file into an executable format and then introducing you to the free independent downloadable install script turning this into a polished application…

There are some additional files that should be added to the install script setup procedure.

MS Access Tools: How To Convert And Deploy An Access Database File As An Executable (ACCDE Or MDE) – My Comments

The additional files should include the Microsoft Access run-time application if the end user or client doesn’t have this application as part of their suite of applications, a polished looking splash screen image file, icon image file that your database may need to point to and any documentation (namely the help files) added to help provide the support and resources for your users.

ms access tools

These are added via the wizard install script setup as shown in the video tutorial and adds the finishing touches to your database which I think should really part of the MS Access tools armoury.

Here’s the link to the Inno Setup Download courtesy of JRSoftware website.

At any time you can convert your database into an executable file format but in reality all design and testing should be carried in a quality controlled environment which means getting other members of your team to complete any test analysis sheets and report of any bugs and missing functionality to save the awkward moment with clients and of course avoiding the many re-runs of building your installation scripts.

The final point to note is that I user a standard vanilla workstation which doesn’t have any of the MS Office applications installed so that I can run this install script and observe the outcome and test as if I were the end user too just to rule out any unexpected errors.

This entry was posted in MS Access, Utilities and tagged , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Confirm you are human.