LUKE_PRYOR
asked on
Creating Restricted Access to a database
So I recently finished(well lets just say its finished) a database and I would like to set up multiple entities to view and utilize the database. I have one person specifically who will need access to one form, one query and maybe one additional table. Im still confused on the best way to do this though. SHould i create a custom menu or is there an easier way to do it. I just dont want a novice to have the ability to effect any of my other tables/queries and I dont want to confuse a very computer illiterate person with an abundance of objects. If you could at very least point me in the right direction I would appreciate it. Thanks
Luke P
Luke P
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok additional info...
I have basically no VBA experience aside from copying and pasting some code I've found on the web... Uh oh right...
So... What you are saying is that I need to have a form open on entry? Then based on the resulting info of this form(input) it would open up the database in either restricted or standard view? Im fine with just two for now, but my next database is going to be way more advanced(much to my dismay...) so possibly at least seeing more advanced options might temper my expectations.
Also,
In the first suggestion BCUNNEY would i need to set every object as false as far as visibility?
Sorry for the dumb questions, I feel all alone in this world of VBA and SQL, there are a lot of resources, but not enough time to figure out the best ways of doing things. Thanks
Luke
I have basically no VBA experience aside from copying and pasting some code I've found on the web... Uh oh right...
So... What you are saying is that I need to have a form open on entry? Then based on the resulting info of this form(input) it would open up the database in either restricted or standard view? Im fine with just two for now, but my next database is going to be way more advanced(much to my dismay...) so possibly at least seeing more advanced options might temper my expectations.
Also,
In the first suggestion BCUNNEY would i need to set every object as false as far as visibility?
Sorry for the dumb questions, I feel all alone in this world of VBA and SQL, there are a lot of resources, but not enough time to figure out the best ways of doing things. Thanks
Luke
<I feel all alone in this world of VBA and SQL, there are a lot of resources, but not enough time to figure out the best ways of doing things.>
I understand...
As you will learn, there is really no "Best" way to do something that works for all situations, ...this is the mostly confusing part and it will only become clearer with experience.
;-)
Things like this should really only be considered *after* the DB is fully functional.
This way setting up forms instead of giving users directl access to tables and queries is not a new concept.
So again, can you explain your ultimate goal with this system, or is this system just to restrict this one user...?
JeffCoachman
I understand...
As you will learn, there is really no "Best" way to do something that works for all situations, ...this is the mostly confusing part and it will only become clearer with experience.
;-)
Things like this should really only be considered *after* the DB is fully functional.
This way setting up forms instead of giving users directl access to tables and queries is not a new concept.
So again, can you explain your ultimate goal with this system, or is this system just to restrict this one user...?
JeffCoachman
ASKER
I would say that my database is fully funtional. I have some housekeeping to do and to possibly reformat some queries, but its doing what I intended it to do.
My Ultimate goal is to share this database on our server (Originally 2 unique users, but if I can figure out the work flow better there might be more eventually. Overall I would be the only person who would do any design work ever and he is the only one who would do data entry) which would allow him to do data entry and data correction and that is all. I might eventually roll more things out to him as he proves capable, but for now baby steps.
Is this enough info? I sometimes have success with google, but this has led me on a wild goose chase. Thanks
Luke
My Ultimate goal is to share this database on our server (Originally 2 unique users, but if I can figure out the work flow better there might be more eventually. Overall I would be the only person who would do any design work ever and he is the only one who would do data entry) which would allow him to do data entry and data correction and that is all. I might eventually roll more things out to him as he proves capable, but for now baby steps.
Is this enough info? I sometimes have success with google, but this has led me on a wild goose chase. Thanks
Luke
<My Ultimate goal is to share this database on our server>
To be sure, is the db "Split"
Are you creating an .accde file for the end user(s)
Then as I stated, you can do this by only designing your user interface around Forms.
The you can use BCUNNEY's suggestion to determine what user is in the DB, and allow or deny access to any form.
But again, this would be "simple" security.
Meaning, a savvy or malicious user may be able to bypass it relatively easily.
And if this evolves beyond a handful of users, it will be inadequate and a more robust security model will be needed.
;-)
JeffCoachman
To be sure, is the db "Split"
Are you creating an .accde file for the end user(s)
Then as I stated, you can do this by only designing your user interface around Forms.
The you can use BCUNNEY's suggestion to determine what user is in the DB, and allow or deny access to any form.
But again, this would be "simple" security.
Meaning, a savvy or malicious user may be able to bypass it relatively easily.
And if this evolves beyond a handful of users, it will be inadequate and a more robust security model will be needed.
;-)
JeffCoachman
Meaning your one user would not be using a Table and a Query, but rather viewing (accessing) this info via a "Form"
So this requires some design foresight as well.