Adding Security groups

[Guest]

I'm trying to use one master database with a second copy where my tables are
linked located in another location. I have completed this, but now I need to
secure the data base so that one group has full access and a second can only
view specific reports and or forms that I choose. Can I create two seperate
switchboards that open based off of a password and then lock all other
options from being able to be viewed.

 

[Joseph Meehan]

I'm trying to use one master database with a second copy where my
tables are linked located in another location.

I am not clear about what you are doing here. I am guessing you are
making a split database with a BackEnd containing the tables and one or more
front ends containing queries, reports and forms. Each user should have
their own copy of the front end on their own machine and the back end should
be located on a server so that everyone accessing it has full (read, write,
modify, create and delete) rights.

I have completed this,
but now I need to secure the data base so that one group has full
access and a second can only view specific reports and or forms that
I choose.

If you have done the split properly you don't need to secure the
database because each user will have their own copy of a front end and the
reports and forms are there.

Of course this does not stop them from creating their own forms and
reports. But if you make that Front End a MDE rather than an MDB that will
remove their ability to change or create forms reports etc.

Can I create two seperate switchboards that open based off
of a password and then lock all other options from being able to be
viewed.

This makes me think you have not split the database like it appears you
should have.

Now if you want to limit their access to data, then you should consider
user level security. Much stronger than passwords, but also harder to set
up and easier to mess up.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

 

[Guest]

Thanks Joseph, would splitting the database be the better option and if so,
do you have a link that would share this prcedure?

I'm trying to use one master database with a second copy where my
tables are linked located in another location.

I am not clear about what you are doing here. I am guessing you are
making a split database with a BackEnd containing the tables and one or more
front ends containing queries, reports and forms. Each user should have
their own copy of the front end on their own machine and the back end should
be located on a server so that everyone accessing it has full (read, write,
modify, create and delete) rights.

I have completed this,
but now I need to secure the data base so that one group has full
access and a second can only view specific reports and or forms that
I choose.

If you have done the split properly you don't need to secure the
database because each user will have their own copy of a front end and the
reports and forms are there.

Of course this does not stop them from creating their own forms and
reports. But if you make that Front End a MDE rather than an MDB that will
remove their ability to change or create forms reports etc.

Can I create two seperate switchboards that open based off
of a password and then lock all other options from being able to be
viewed.

This makes me think you have not split the database like it appears you
should have.

Now if you want to limit their access to data, then you should consider
user level security. Much stronger than passwords, but also harder to set
up and easier to mess up.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

 

[Joseph Meehan]

Thanks Joseph, would splitting the database be the better option and
if so, do you have a link that would share this prcedure?

I don't know your specific needs and situation so I can't say what would
be the "better" option. However I would say that 99% of the time when you
are going to have two or more users sharing data and a good server based LAN
is available that you should split the database.

Access has a Wizard to split a database. Look under Tools - Database
Utilities. Use a copy of your original. The process is easy (unlike
adding user level security) but errors can happen.

I'm trying to use one master database with a second copy where my
tables are linked located in another location.

I am not clear about what you are doing here. I am guessing you
are making a split database with a BackEnd containing the tables and
one or more front ends containing queries, reports and forms. Each
user should have their own copy of the front end on their own
machine and the back end should be located on a server so that
everyone accessing it has full (read, write, modify, create and
delete) rights.

I have completed this,
but now I need to secure the data base so that one group has full
access and a second can only view specific reports and or forms that
I choose.

If you have done the split properly you don't need to secure the
database because each user will have their own copy of a front end
and the reports and forms are there.

Of course this does not stop them from creating their own forms
and reports. But if you make that Front End a MDE rather than an MDB
that will remove their ability to change or create forms reports etc.

Can I create two seperate switchboards that open based off
of a password and then lock all other options from being able to be
viewed.

This makes me think you have not split the database like it
appears you should have.

Now if you want to limit their access to data, then you should
consider user level security. Much stronger than passwords, but
also harder to set up and easier to mess up.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex
product with a very steep learning curve. Properly used it offers
very safe versatile protection and control. However a simple
mistake can easily lock you out of your database, which might
require the paid services of a professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

 

[Albert D. Kallal]

"Basic to Intermediate user"

Thanks Joseph, would splitting the database be the better option and if
so,
do you have a link that would share this prcedure?

"be the better" option can only be decided by you based on your particular
needs.

However, to complete hide the ms-access interface, and keep users out of the
application, you don't need to setup security, but can use the
tools->start-up options.

Any application you write in access of any complexity, and it will be
multi-user...splitting is a real must anyway....

I explain how and why here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

If you do split, then you can simply distribute a different mde to one group
of people,and another for those that need more/different features or reprots
to run...

 

[Albert D. Kallal]

You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

If you split your database, and give each user a mde, then they can't modify
the designs of the forms. So, give each user a mde, and not a mdb. This will
prevent them from design changes....

You can read about splitting here...

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm