Question Run time

Lanason

Registered User.
Local time
Today, 22:19
Joined
Sep 12, 2003
Messages
258
I have written a database used by a number of my staff. But I want to prevent them from using the std access buttons, menus, access the data tables.

The tables are in a separate DATA database and linked to the APP Database, which contains the forms, querys, reports etc

i.e. only to use the forms i have designed.

Is this easy - if so how do i do it?:confused:
 
You can hide the menu bar/ribbon, database window.
This has been discussed many times on this forum, just do a search.

Catalina
 
You can hide the menu bar/ribbon, database window.
This has been discussed many times on this forum, just do a search.

Catalina

what are the best keywords for the search ??
 
Did a search and came up with

DoCmd.ShowToolbar "Ribbon", acToolbarNo

stupid question but if I put this on my version of the Database, how do I get into it to modify it. Cant the "smart" colleagues, then do the same !!
 
Look for - disable bypass shift key. And before you start playing around with this make sure you have several backups in case you lock yourself out.

When you finally distribute the application, compile it to an .accde and then rename it to .accdr
The .accdr file type tells Access to pretend to be the runtime engine. With this extension, the user will not be able to get into design view or even see any database objects no matter what he does. Of course, if he thinks to rename it back to .accde, he will be able to get into the database if he can also get past the disallow shift bypass code.
 
Look for - disable bypass shift key. And before you start playing around with this make sure you have several backups in case you lock yourself out.

When you finally distribute the application, compile it to an .accde and then rename it to .accdr
The .accdr file type tells Access to pretend to be the runtime engine. With this extension, the user will not be able to get into design view or even see any database objects no matter what he does. Of course, if he thinks to rename it back to .accde, he will be able to get into the database if he can also get past the disallow shift bypass code.

Thanks - how does one "compile" the application - is there a menu option for this?
 
Compiling is the process of taking human readable code such as VBA or C# or COBOL, etc and converting it into machine readable code. For real compiled languages (not VBA) the output of the compiler would be an .exe file. For Access VBA, which is an interpreted language rather than a true compiled language, the output is an .accde which has had all the source code removed. Make sure you save the original .accdb because there is no going back without it. If you need to make future changes, you need to go back to the .accdb, make the changes, and compile into an .accde again.
 
Compiling is the process of taking human readable code such as VBA or C# or COBOL, etc and converting it into machine readable code. For real compiled languages (not VBA) the output of the compiler would be an .exe file. For Access VBA, which is an interpreted language rather than a true compiled language, the output is an .accde which has had all the source code removed. Make sure you save the original .accdb because there is no going back without it. If you need to make future changes, you need to go back to the .accdb, make the changes, and compile into an .accde again.

Dear Pat - I understand what a compiler does - I used "Fortran cards"
back in the 80's. Just dont know how to instigate it in Access ....
 
For A2010 - look under save and publish from the File menu. With different versions, the .mde/.accde option will be in different places. It is one of MS's favorate features to move around.
 
For A2010 - look under save and publish from the File menu. With different versions, the .mde/.accde option will be in different places. It is one of MS's favorate features to move around.

Dear Pat,

I'm using access 2003 - and have now created the .mde file - do i need to rename it?
 
You can't. The .accdr trick only works with A2007-A2010 databases.
 
Try to open a form/report/module in design view and you will see that you can't. Keep the original .mdb safe. You will need to go back to it if you need to make any changes.
 
Try to open a form/report/module in design view and you will see that you can't. Keep the original .mdb safe. You will need to go back to it if you need to make any changes.

Super so that sorts the code from getting edited - now all I need to do is hide the ribbon and menus in the mde of course.....

I'm entering new ground here, so please be patient with me
if I put:-
DoCmd.ShowToolbar "Ribbon", acToolbarNo
in the code of the Main menu form that "autoexec" opens,

Q1 - Will it then stop me going in and editing the original code as well
Q2 - does it also apply to all forms until reversed somewhere in the code
Q3 - would a button with say a hard encoded password allow me a back door way in to my MDB, before I compile it.

In 25 years of totally amateur programming (Smartware, Paradox, FoxPro, dBase etc then Access) - I've never tried to "lock it up" against people being "smart".
 
Last edited:
Look at the startup options. You will have the option of hiding the database window and other menus and toolbars.
 

Users who are viewing this thread

Back
Top Bottom