How to deploy my Ms Access the right way?

[bmkol]

Hi
After I finished my project that has 2 files (splitted) .... how do I deploy it to customers with no chance to make chenges and to be able to install it in any computer (even if they don't have Access ... runtime)?

 

[CJ_London]

if they don't have a full version of access, they will need the runtime. If they are using runtime then your app needs to allow for that since runtime does not have certain functionality such as navigation window, ribbon and right click menus. And their computer needs to have windows OS

FE should be a .accde or .accdr to prevent users with a full version editing the forms/report/modules

if compiled to .accde/r you will need to know which version of access the user will be using - 32bit or 64 bit as the user might be using either. Note a user cannot have both versions on their computer.

Other issues are when the user installs, you have no control of where they install the FE and BE so you need to provide a facility for relinking. And the user may be using an earlier version of access - so ensure you provide files that do not use functionality/objects etc from later versions

I would look at using an installer which creates a .exe installation file which the user can run

look to the bottom of this thread - a number ask the same question

 

[Ranman256]

I have an access app to distribute the latest FE copies to all users.
This way their shortcut always opens the correct version.

 

[theDBguy]

Hi. To run an Access database, the user needs the Access application (full version or runtime). Without any Access application (including Runtime), then they won't be able to open the database.

 

[oleronesoftwares]

I have an access app to distribute the latest FE copies to all users.
This way their shortcut always opens the correct version

So if you have an access app(do you mean a copy of ms access that can be installed on each system)

If that is the scenerio then,your access database(front end must have a routine that checks for the location of the backend, whenever it loads, and if the location is broken, it should prompt the user to re-link it, the re-link functionality should be at the click of a button, macros can do that.

You can also have user table, user rights created that will limit access to some features ,so users at the front end can focus on just using the application.