Home/ Questions/Q 9067637
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-16T16:59:31+00:00

I have a simple question. I am new to the development world, and have

  • 0

I have a simple question. I am new to the development world, and have created some fairly decent access databases. These databases are geared towards the small business owner. Currently I have a few small businesses whom are interested in the databases that I have created as a potential product to purchase. How and what is the best way to go about packaging an access database so that the user does not have to have a full copy of access, and also so that the product can be updated in the future. For instance version 1.1 might be the launch version, but 1.2 may contain the date and time on the splash screen of the database?

If more information is needed please let me know I will be glad to upload more information.

The Access database that I am using is Access 2013.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here is a simple setup that has worked for me:

    • Convert to .accde.
    • Give users Access Runtime.
    • Split Database.
    • Place updated frontend into Dropbox account shared with client.
    • Instruct client how to find backend when prompted using the following code on your startup screen load event.


    Private Sub Form_Load()
    On Error GoTo frm_error
    Dim RS As Recordset
    Dim cn As Database
    Set cn = CurrentDb
    Set RS = cn.OpenRecordset("tblX") 'Insert name of any table in backend
    RS.Close
    Exit Sub
    frm_error:
    If MsgBox("Database cannot be found. Advanced Users press OK to link the tables. Otherwise, notify an admin and press cancel to close the xProgram.", vbOKCancel) = vbOK Then
    RunCommand acCmdLinkedTableManager
    Else
    DoCmd.Quit
    End If
    End Sub

    I will note that I have since stopped using access as a backend and switched to SQL Server hosted by Amazon RDS. This does wonders for security, backup, front-end upgrades, and off-site maintenance (though I will stress that you will never get a fully secure system using access as a frontend).

    • 0