Big_Harry1
asked on
How do I prevent the users of MSACCESS 2003 runtime projects from opening in the development window with the "shift" key?
I am writing small MS Access 2003 databases for various applications then packaging as a "Runtime' application. I want to secure the runtime version of the db so that no hot key will allow the user with MS ACCESS to open the db in a developer window. Is this possible when packaging or is there another software available for securing the database?
dannywareham
www.mvps.org/access/general/gen0040.htm
It's worth noting that, even if you secure the bypass key (shift), a user with a full installation of Access could create a new database and import your objects into theirs....
You need to consider Access User-Level Security (ULS) to help secure your objects, too.
:-)
You need to consider Access User-Level Security (ULS) to help secure your objects, too.
:-)
Go to tools->Customize; select the Toolbar tab; click on new and create a new toolbar. Add the commands you want your users to have. Go to Tools->Startup; in the Menu Bar window, select the menu bar you just created; turn off "display Database Window", "Allow Built in Toolbars", "Allow toolbar/menu changes", "Allow Full Menus", "Allow Shortcut Menus", "Use Special Keys" (after clicking advanced). Save the project then create an MDE file, Tools->Database Utilities->Make an MDE file. Distribute the MDE file.
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.
The first post has a different, more secure version - with a fourth arguement:
A Variant (Boolean subtype) that indicates whether or not the Property is a DDL object. The default is False. If DDL is True, users can't change or delete this Property object unless they have dbSecWriteDef permission.
A Variant (Boolean subtype) that indicates whether or not the Property is a DDL object. The default is False. If DDL is True, users can't change or delete this Property object unless they have dbSecWriteDef permission.
