creating a secure interface???

  • Thread starter Thread starter mnance
  • Start date Start date
M

mnance

Is the a way to create a MS database and give the program
to someone else without giving them the ability to change
settings?

I think there is a way to save forms and reports so they
are password protected. I would perfer, instead, that
when someone besides me opens the file [file.mdb], the
only thing that appears on their screen is the user form
that I have designed. I don't even want them to see that
there are tables, queries, etc.

Situation 1:
I've created a database to manage student disciplinary
infractions. It automatically prints parent letters and
disciplinary referrals. Several other teachers have seen
it and have asked for a copy. I've given the program to
a few other teachers at school and am now spending my
time trouble shooting what they have messed up. They
have changed form and report layouts. They have changed
relationships of tables, and so on. I would like for
them to only be able to access the main interface form.
They should not be able to view tables, form, queries, or
reports...and certainly not be able to make changes to
these.

Situation 2:
I've created a testing package for my students in MS
Access. Again, I only want them to be able to view the
single form I've designed for them. They should not have
privilages to change any settings.
 
I would consider delivering the database to your colleagues (or students) as
an MDE file, rather than an MDB file. Saving your Access database as an MDE
file prevents the following actions:

- Viewing, modifying, or creating forms, reports, or modules in Design view.
- Adding, deleting, or changing references to object libraries or databases.
- Changing code - an MDE file contains no source code.
- Importing or exporting forms, reports, or modules. However, tables,
queries, data access pages, and macros can be imported from or exported to
non-MDE databases.

You, of course, would keep a copy of the MDB file so that you can make
changes and improvements.

hth,
 
mnance said:
Is the a way to create a MS database and give the program
to someone else without giving them the ability to change
settings?

I think there is a way to save forms and reports so they
are password protected. I would perfer, instead, that
when someone besides me opens the file [file.mdb], the
only thing that appears on their screen is the user form
that I have designed. I don't even want them to see that
there are tables, queries, etc.

Situation 1:
I've created a database to manage student disciplinary
infractions. It automatically prints parent letters and
disciplinary referrals. Several other teachers have seen
it and have asked for a copy. I've given the program to
a few other teachers at school and am now spending my
time trouble shooting what they have messed up. They
have changed form and report layouts. They have changed
relationships of tables, and so on. I would like for
them to only be able to access the main interface form.
They should not be able to view tables, form, queries, or
reports...and certainly not be able to make changes to
these.

Situation 2:
I've created a testing package for my students in MS
Access. Again, I only want them to be able to view the
single form I've designed for them. They should not have
privilages to change any settings.
Click to expand...

Another option is to use Workgroup Security and password protect everything.
You can fine tune the access permissions to tables, queries, code,
everything. The advantage is that, if it doesn't work first time, everytime,
in every environment you try to install it in, you have all the source code
right there to debug it.

I assume that chopping the fingers off the end users is not a viable option.

larry
 
please be patient with me...

i have the form that i want as the main user interface.
i right-clicked on that and selected "save as/export..."
a dialog box appeared prompting me to either export the
form or same it as a report. i selected export.

a save dialog appeared. i changed the file extention to
formname.mde

an error message appeared that said it could not find the
path i specified.

what am i doing wrong?

i looked in the office reference books i have for more
information. i can't find anything that even mentions
a .mde file extension. what should i be looking for?

by the way---i'm trying to find a good intermediate level
book to help me in access. it would be nice if it had
some SQL language and syntax to help with functions. do
you know of any books that are beyond the "just getting
started" level and not quite at the "i am one with the
computer" level? :)

thanks
-----Original Message-----
I would consider delivering the database to your colleagues (or students) as
an MDE file, rather than an MDB file. Saving your Access database as an MDE
file prevents the following actions:

- Viewing, modifying, or creating forms, reports, or modules in Design view.
- Adding, deleting, or changing references to object libraries or databases.
- Changing code - an MDE file contains no source code.
- Importing or exporting forms, reports, or modules. However, tables,
queries, data access pages, and macros can be imported from or exported to
non-MDE databases.

You, of course, would keep a copy of the MDB file so that you can make
changes and improvements.

hth,
--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX


mnance said:
Is the a way to create a MS database and give the program
to someone else without giving them the ability to change
settings?

I think there is a way to save forms and reports so they
are password protected. I would perfer, instead, that
when someone besides me opens the file [file.mdb], the
only thing that appears on their screen is the user form
that I have designed. I don't even want them to see that
there are tables, queries, etc.

Situation 1:
I've created a database to manage student disciplinary
infractions. It automatically prints parent letters and
disciplinary referrals. Several other teachers have seen
it and have asked for a copy. I've given the program to
a few other teachers at school and am now spending my
time trouble shooting what they have messed up. They
have changed form and report layouts. They have changed
relationships of tables, and so on. I would like for
them to only be able to access the main interface form.
They should not be able to view tables, form, queries, or
reports...and certainly not be able to make changes to
these.

Situation 2:
I've created a testing package for my students in MS
Access. Again, I only want them to be able to view the
single form I've designed for them. They should not have
privilages to change any settings.
Click to expand...


.
Click to expand...
 
Back
Top