DGWhittaker
asked on
Using Accessruntime 2013
I need some clarification on how to use the Access Runtime.
Is this something used on the developers computer to package the solution, or installed on the users computer to operate the solution?
thanks for your support!
Dennis
Is this something used on the developers computer to package the solution, or installed on the users computer to operate the solution?
thanks for your support!
Dennis
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
Access Runtime is distributed to users who do not have a license of Access. The developer will have the full version as run time is a scalled down version.
The runtime is similar to the full version of Access but designed for users to only run existing Access databases. They cannot create their own or modify the design of your databases and some features are missing .
The instructions of how to use is in the below link
http://www.fmsinc.com/microsoftaccess/developer/runtime.html
Access Runtime is distributed to users who do not have a license of Access. The developer will have the full version as run time is a scalled down version.
The runtime is similar to the full version of Access but designed for users to only run existing Access databases. They cannot create their own or modify the design of your databases and some features are missing .
The instructions of how to use is in the below link
http://www.fmsinc.com/microsoftaccess/developer/runtime.html
The runtime is actually the same physical file as the full version and is installed in the same Office folder. When installed as the runtime, it simply hides development features. This is why you would have trouble installing both the runtime and full version for the same version of Access. You can install the runtime for a different version because it gets installed in a different folder but typically, users don't have the full version installed at all so this isn't a problem.
For developers, the best solution is to use a VM for testing with the runtime so you can simulate the user's environment.
When you distribute your FE, compile the app to a .accde and then rename it to .accdr. The .accdr extension tells all versions of Access to pretend to be the runtime and hide all development features. This produces a smoother interface since some actions cause the navigation pane to be displayed and in a user app, you NEVER want them to see the navigation pane.
For developers, the best solution is to use a VM for testing with the runtime so you can simulate the user's environment.
When you distribute your FE, compile the app to a .accde and then rename it to .accdr. The .accdr extension tells all versions of Access to pretend to be the runtime and hide all development features. This produces a smoother interface since some actions cause the navigation pane to be displayed and in a user app, you NEVER want them to see the navigation pane.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks All!
I found it helps to have an autoexec Macro to get things started for my runtime users. (my bad,)
Dennis
I found it helps to have an autoexec Macro to get things started for my runtime users. (my bad,)
Dennis
you can not edit, create objects in the runtime version.
in the FULL version, you can create/ modify objects, write/edit codes
see this link for more info