Creating a Runtime version in Access 2010
I have an older Access database that I have upgraded to Access 2010 (.accdb format). I am trying to create a runtime version of this database so that users who don't have Access installed on their workstations can open the database and run queries and reports, but of course not enter new data. This is a VERY simple database - just a few tables, a few queries and one report. I've done this before with some other databases, but this one for some reason isn't working.
I'm using the Package Wizard from the Access 2010 application. Creating the package appears to work fine, and so does the installation process. But when I try to open the database, all I get is the Files tab - no Home tab and therefore no contents in the database at all. The Home tab appears briefly with a message about trusting the contents of the database, but when I click OK to open the DB, the Home tab disappears. Is there some security or permissions setting that I'm missing? The .accdr file is being saved to the user's My Documents folder, so they have full control of that location.
I'm using the Package Wizard from the Access 2010 application. Creating the package appears to work fine, and so does the installation process. But when I try to open the database, all I get is the Files tab - no Home tab and therefore no contents in the database at all. The Home tab appears briefly with a message about trusting the contents of the database, but when I click OK to open the DB, the Home tab disappears. Is there some security or permissions setting that I'm missing? The .accdr file is being saved to the user's My Documents folder, so they have full control of that location.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Creating the form worked perfectly - I discovered too that if you're not too picky about the way the form looks, creating a form from a table in Access 2010 is almost TOO easy!
The one problem I see is that the security warning message pops up every time they open the database. Anyone know of a way to prevent this? It's not too big a deal, just an annoyance because it appears every time.
The one problem I see is that the security warning message pops up every time they open the database. Anyone know of a way to prevent this? It's not too big a deal, just an annoyance because it appears every time.
Hi,
you can stop that by adding the folder where the database file is saved on the user's computer to the trusted locations. For this, open the Access options and there the trust center, there you can find the trusted locations where you can add any folder (and optional any subfolder of the selected folder) to the trusted locations. All Access files which are saved into this folder (or subfolder) will be executed without the security warning.
Cheers,
Christian
you can stop that by adding the folder where the database file is saved on the user's computer to the trusted locations. For this, open the Access options and there the trust center, there you can find the trusted locations where you can add any folder (and optional any subfolder of the selected folder) to the trusted locations. All Access files which are saved into this folder (or subfolder) will be executed without the security warning.
Cheers,
Christian
ASKER
Hi, Christian. Thanks for the response. The problem is that in the Access Runtime version, the user can't set the trusted locations from the application. I suppose it's probably a registry entry that I'll have to find and edit through a login script or something. I just thought someone might know this right off the bat and allow me to be lazy and skip the process of researching it myself ;-)
ASKER
Thanks guys!
Hi,
you can offer this option to the user with this command:
This opens the Options dialog directly, you can use it in a button or menu. Problem with this is that it also opens other options to the user which you may not want the user to change it (for example timeout values for ODBC calls or whatever). I inserted this command in my applications in an admin menu only so only admins can change the options here.
Cheers,
Christian
you can offer this option to the user with this command:
DoCmd.RunCommand acCmdOptionsThis opens the Options dialog directly, you can use it in a button or menu. Problem with this is that it also opens other options to the user which you may not want the user to change it (for example timeout values for ODBC calls or whatever). I inserted this command in my applications in an admin menu only so only admins can change the options here.
Cheers,
Christian
ASKER