Startup issues

[hermanko]

Hi,

I have database ready to be used within my department, but I am
wondering about how to secure it so that only I have the ability to
make changes, whereas the users can only make changes thru the
available forms.

I have unchecked all that i needed from the Tools-->Startup, and have a
form set to open on startup as my "main menu". However, i can still use
keyboard shortcuts like, CTRL-N, even tho they no longer show up in the
menu bar (i have it blank)....so it doesn't seem secure, really.

what are my options? Do i need to convert the file to .mde? what does
that accomplish? Or do i need to go into the Security settings and play
around with that?

Thanks
Herman

 

[Larry Daugherty]

Hopefully, you have already split your application and the BackEnd is
in a folder on the server that is available to all of your users.

Yes, naked an MDE and place a copy on each user's pc. Before you
make the MDE, make sure that your MDB is linked to the BackEnd on the
server. That has to be the same relative address for all users. Once
you've done that, make the MDE. and distribute copies. Only you, the
developer, should have access to the MDB of the front end.

HTH

 

[hermanko]

I am not at the stage of splitting my database up as of yet. Actually,
i don't know if it will be put on a network at this time. For now I am
just wondering how i keep users from being able to change the database
structure/objects.

For example, my Main Menu switchboard has the "exit" database command.
However, what is stopping a user from clicking the "X" or Close command
from the Access menubar and terminating my database all together? My
database is designed such that the use should exit thru the switchboard
to complete the process, and not do it prematurely thru the Access
menubar....

Would you be able to describe how i can achieve this?
thanks

 

[Joseph Meehan]

Hi,

I have database ready to be used within my department, but I am
wondering about how to secure it so that only I have the ability to
make changes, whereas the users can only make changes thru the
available forms.

I have unchecked all that i needed from the Tools-->Startup, and have
a form set to open on startup as my "main menu". However, i can still
use keyboard shortcuts like, CTRL-N, even tho they no longer show up
in the menu bar (i have it blank)....so it doesn't seem secure,
really.

what are my options? Do i need to convert the file to .mde? what does
that accomplish? Or do i need to go into the Security settings and
play around with that?

Thanks
Herman

Access offers you several tools. Which one is best depends on the
specifics. Since you don't yet know if it is even going to be shared on a
LAN, it may be a little too early to choose the best security plan.

 

[Larry Daugherty]

Before you start using your application in earnest and certainly
before you let users get at it, you need to split it.

To handle the specific issue you just raised, you'd have to get at the
form in design view and play with the properties.

My advice would be to not trap your users and force them to do
anything that's not absolutely necessary. In the case you mention,
you might start a war that you can't win. If you won't let users
close out of your application when they want they can (and will)
either hit CTRL-ALT-DEL or hit the power switch. If they hit the
power switch with Access open you will find that Access will have a
high rate of corruption. The users won't be blamed, you will. If
users don't like you or your software, you've got troubles. Again, my
advice would be to maintain friendly relations with all who will use
your application. Solicit their suggestions, some may be very good.

There are times when users can get themselves into trouble and they
want to get out of the application leaving things as they were. Go
out of your way to anticipate those issues and give them a way out.
Make it easy for them by placing large navigation buttons and a "Done"
button on each form in the same place. Unless you've done something
to change things, when the form closes you should automatically return
to the Form or Switchboard that called it. Put a "Done" or "Quit"
button on every switchboard.

One more note: There should be absolutely no difference to Access in
what happens when the user chooses a quit/done button from the
Switchboard or clicks the X in the upper right corner. If you have
cleanup code that only executes in the one place you need to handle it
differently so that it doesn't matter where the Quit command came
from.

There may be some relevant help on www.mvps.org/access It is a great
place to find lots of Access lore.

HTH

 

[hermanko]

When i refer to the "X" in the upper right corner...I don't mean for
the Switchboard. I have functionality in place for that already, but I
am talking about the "X" in the Microsoft Access program itself. I
already have an option to "EXIT" from the switchboard that will close
the db as well as the Access program. How do i account for when a user
closes the Access program pre-maturely (i.e. does not go thru the
switchboard "EXIT" option)? This is why i am askign if there's a way
for the database to be opened and NOT have the access background
visible?

 

[Larry Daugherty]

Access goes a long way toward protecting your application in those
cases. Objects are closed in the reverse order of their opening:
Last opened, first closed. If there is validation code that runs when
a form is closed, it will be run.

WHY do you insist that the user close the application from the one and
only place you intend? What service of benefit to the application and
its data is delivered by insisting on that path that wouldn't be
automatically provided by closing from somewhere else? If there is no
technical reason for doing it then don't.

My responses here are intended to help you, the Access application
developer, provide a good application for yourself and your users.
It's not about me telling you what to do.

There are books about user interface design. I recommend that you
look at a few.

If you choose to continue this thread, you might start by explaining
the specific harm you anticipate that a user would cause by closing
Access by clicking the Close button.

Have you visited www.mvps.org/access ?

HTH

 

[hermanko]

Larry,

I understand what you are explaining. The design must be flexible
enough so that the user isn't trapped. My question, then, is how do i
"do something" IF the Access program is closed by either "File-->Exit"
or the "X" button? I've been learning Access for 2 months and so this
is not familiar to me. What do u mean by validation code? And what is
the process of "protecting" my database if, say, the computer is
switched off manually?

Thanks,
Herman

 

[Guest]

When Access is running (.mdb or .mde) it provides a number of short cut keys
as follows :-
Control + N Start new database
Control + O Open database
Control + S Save database
Control + P Print current window
Control + X Cut current object
Control + W Close current window
Control + G Open debug window
F1 Open Access Help

It is possible to disable these function as follows :-
Open the main database window and choose Macros.
Click New and name the Macro 'Autokeys' (without the quotes). This is a
special Access macro.
In the first row under the Macro Name column enter ^N, leave the Action
field blank.
In the following rows enter ^O, ^S, ^P, ^X, ^W and ^G.
To disable the F1 key help facility enter {F1}
Click Save to save the Macro and then close it.

Note that you could, if you wanted, open a form in your database with these
keys (or any of the others) by entering Open Form in the Action field and
then

choosing a form in the Form Name property section at the bottom of the form.

To disable the Access Close (X) button and the Files -> Exit options do the
following :-
In your main module add the line

Public gCloseAccess As Boolean

In the Form_Unload event of the Switchboard form enter :-

Cancel = Not gCloseAccess

In the HandleButtonClick function (assuming you are using the Access
Switchboard form) enter this code just before the Application.Quit command :-

gCloseAccess = True
Application.Quit


Also visit
http://www.kayodeok.btinternet.co.uk/favorites/kbofficeaccesshowto.htm for
more help


Hope that helps.

 

[Larry Daugherty]

If the computer is turned off, you are screwed! That will very likely
damage the application. You want to do everything you can to make
your application user friendly so that people don't get frustrated and
just turn off the machine.

If you need to execute cleanup code as your application is closed,
there is a way. It involves opening an invisible form when your
application starts and never closing it. When Access closes that form
will be the last thing closed. Put your cleanup code in the Close
event of that form. Using that method your cleanup code will be
executed when Access is closed from within its running environment.

Look in Help for "validation". In general it is checks that you can
put into the application to assure that data is entered in a valid
format or state of completion.

Have you visited www.mvps.org/access ?

HTH