psbsmms
Programmer
- Dec 14, 2001
- 74
Is there a way to shut off the debugger for access 2000 db so useres don't get into the VBA programming
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
De Bugger
- Thread starter psbsmms
- Start date
- Status
You can't exactly shut off the debugger, but there are several ways to keep users out of your code.
An easy way is to convert your application into an MDE file, using Tools|Database Utilities|Make MDE File. This makes a copy of the database but without copying the source code. Modules in the database window will be disabled, so they can't be opened. Anything that would have caused a break in code, such as pressing Ctrl-Break, will result in a runtime error instead (and the application will shut down). You'll need to keep your original MDB file for development, but distribute copies of the MDE file.
A more complex way, but one which is friendlier to the users, is to set the Startup properties (Tools menu) to hide the database window and disable the Access Special Keys (which include Ctrl-Break and Ctrl-G for the Debug window). However, you'll have to give them another way to open tables, queries, forms and reports, and to execute any macros you have. The Switchboard Manager will help you build a form that provides them buttons for this purpose.
You could also use Access' built-in security features to deny your users Read Design permission on the code modules. If you already have Access security in the application, this could be the best approach, but if you don't it's probably better to use one of the other methods. Rick Sprague
An easy way is to convert your application into an MDE file, using Tools|Database Utilities|Make MDE File. This makes a copy of the database but without copying the source code. Modules in the database window will be disabled, so they can't be opened. Anything that would have caused a break in code, such as pressing Ctrl-Break, will result in a runtime error instead (and the application will shut down). You'll need to keep your original MDB file for development, but distribute copies of the MDE file.
A more complex way, but one which is friendlier to the users, is to set the Startup properties (Tools menu) to hide the database window and disable the Access Special Keys (which include Ctrl-Break and Ctrl-G for the Debug window). However, you'll have to give them another way to open tables, queries, forms and reports, and to execute any macros you have. The Switchboard Manager will help you build a form that provides them buttons for this purpose.
You could also use Access' built-in security features to deny your users Read Design permission on the code modules. If you already have Access security in the application, this could be the best approach, but if you don't it's probably better to use one of the other methods. Rick Sprague
- Status
Similar threads
- Locked
- Question
- Locked
- Question
