472,119 Members | 1,480 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,119 software developers and data experts.

Force my Database to Open with Runtime Only

I have created a simple databse in access 07 now I wan to open it with runtime only even if user having full version of access 07.how I do it. And i want to package and develop my databse with installer so which softwares are needed for it.
May 17 '16 #1
5 6277
Seth Schrock
2,965 Expert 2GB
There are a couple of ways to do this. First, you can rename your file to have a .accdr file extension. Or you can create a shortcut to the database and change the target to be
Expand|Select|Wrap|Line Numbers
  1. "Path to Access" "Original target path" /Runtime
So an example would be (this is for Access 2010)
Expand|Select|Wrap|Line Numbers
  1. "C:\Program Files\Microsoft Office\Office14\MSACCESS.EXE" "C:\MyDatabase.accdb" /Runtime
May 17 '16 #2
Thank for your response. Seth. . But these are easily undo by user so I want to permanently set db to open with runtime only.
May 18 '16 #3
Seth Schrock
2,965 Expert 2GB
There is nothing that can't be undone by the user. If you are just trying to protect the database from changes, then you can make the database into an executable file (.accde). It will still open using the full version of Access, but no design changes are allowed. You would need to keep the original file in case there are any bugs that need fixed, but you could just publish the executable file to everyone else.
May 18 '16 #4
Ok and Thank you seth.....
May 18 '16 #5
5,501 Expert Mod 4TB
*.accde is mostly what I do when I need to protect the design. As Seth pointed out, and I cannot stress enough, make sure you keep a copy of the "development" database. We had an instance where someone "accidently" created the executable version using the only copy of the front-end database... and of course, years later changes needed to be done. Had to rebuild everything from scratch.

+ The downfall of the runtime environment is two fold in that you have to create all of the menus that you want the user to have AND all of your code must have proper error handling. While the latter is something that should be done as good coding practice, the former has become more difficult for the beginning to intermediate programmer with the advent of the "Ribbon" to replace the old menu/command-bars. The executable is a nice compromise with protecting the main interface as well as allowing the user to interact with the common Ribbon tools.
May 20 '16 #6

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

23 posts views Thread by Markus | last post: by
3 posts views Thread by Spam Catcher | last post: by
1 post views Thread by Chris Fairles | last post: by
4 posts views Thread by jabslim via DotNetMonster.com | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.