user access

[Guest]

Hi, I have designed quite a large database and am ready to put it on our
server to let people access it. I was wondering what steps I should do in
order to do this. I have heard information on splitting and making it an MDE,
and just wanted some input. There will be two basic types of users.

1) Full access users - Able to use forms, look at tables, code, etc.
2) Limited access users - I want these ones only able to use 6 forms I have
designed for them. I don't want them able to get into design view, the code,
etc. I also don't want to give them access to the tables, queries, etc. With
this said though, I think they will need permission to delete records and add
recrods to tables because once in a form, if they mess up, they can hit a
clear button which essentially deletes the record they have just made, but no
others.

Thanks for your help on lauching my creation

 

[Keith Wilby]

Hi, I have designed quite a large database and am ready to put it on our
server to let people access it. I was wondering what steps I should do in
order to do this. I have heard information on splitting and making it an
MDE,
and just wanted some input. There will be two basic types of users.

1) Full access users - Able to use forms, look at tables, code, etc.
2) Limited access users - I want these ones only able to use 6 forms I
have
designed for them. I don't want them able to get into design view, the
code,
etc. I also don't want to give them access to the tables, queries, etc.
With
this said though, I think they will need permission to delete records and
add
recrods to tables because once in a form, if they mess up, they can hit a
clear button which essentially deletes the record they have just made, but
no
others.

Thanks for your help on lauching my creation

I'm not sure why you would want any of your users to view your design, code
etc but that being the case just give them a copy of your mdb and give your
limited users a copy of an mde made from an mdb with hidden queries and only
the 6 required forms in it. Anything more complex will probably required
you to implement user-level security (difficult if you're new to it).

HTH - Keith.
www.keithwilby.com

 

[Guest]

How do I hide the queries, tables and forms (other than the six), etc. when
making it a MDE?

 

[Keith Wilby]

How do I hide the queries, tables and forms (other than the six), etc.
when
making it a MDE?

Right click the query icon and select "properties".

Keith.

 

[Guest]

Ha, easy enough

Would you recommend splitting the database as well? If so, would I split
then make it an MDE or vice versa?

 

[Keith Wilby]

Ha, easy enough

Would you recommend splitting the database as well? If so, would I split
then make it an MDE or vice versa?

If you have more than one user then I would recommend splitting. Make the
FE an mde, there is no mileage in making the BE an mde so leave it as an
mdb.

 

[Guest]

Great. Since I two types of users, ones that can have full access to
everything (including code, design view, etc) and ones with only access to
the six forms which would they all use? I assume the limited access users
would use the front end MDE with the hidden forms, queries, etc and the full
access users (which need to be able to simultaneously update tables, use
forms, run queries, etc with each other and with the limited access users)
would use the front end MDB???? Sorry for probably the dumb questions, but I
am all new at lauching a database

--Michael

 

[Keith Wilby]

Great. Since I two types of users, ones that can have full access to
everything (including code, design view, etc) and ones with only access to
the six forms which would they all use? I assume the limited access users
would use the front end MDE with the hidden forms, queries, etc and the
full
access users (which need to be able to simultaneously update tables, use
forms, run queries, etc with each other and with the limited access users)
would use the front end MDB

Got it in one