If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Security for database - user accounts and log on
I have created, split my database, but have concerns about security on the
be, I have made the FE (mde) to place on each user's pc but i am wondering is it necessary for me to create user accounts? |
#2
|
|||
|
|||
Security for database - user accounts and log on
What are your concerns? If all the users can have access to the data, but
non-users shouldn't, then password protecting the FE and BE could be good enough. However if you only want the users to see some of the data; or be able to only enter or edit records, but not delete (for example); or messing with the design of the tables orqueries, then you need to implement User Level Security or you could just password protect the BE and not tell the users. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Chantel33" wrote: I have created, split my database, but have concerns about security on the be, I have made the FE (mde) to place on each user's pc but i am wondering is it necessary for me to create user accounts? |
#3
|
|||
|
|||
Security for database - user accounts and log on
if i make the the fe a mde, then i won't need to worry about table, queries
and reports messed up correct? "Jerry Whittle" wrote: What are your concerns? If all the users can have access to the data, but non-users shouldn't, then password protecting the FE and BE could be good enough. However if you only want the users to see some of the data; or be able to only enter or edit records, but not delete (for example); or messing with the design of the tables orqueries, then you need to implement User Level Security or you could just password protect the BE and not tell the users. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Chantel33" wrote: I have created, split my database, but have concerns about security on the be, I have made the FE (mde) to place on each user's pc but i am wondering is it necessary for me to create user accounts? |
#4
|
|||
|
|||
Security for database - user accounts and log on
Not entirely correct. They will not be able to mess with the reports in a FE
MDE. However the users can still mess with the queries and any tables that you put in the FE. Also unless you do something like password protect the BE, the users could get into it and mess with the tables. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Chantel33" wrote: if i make the the fe a mde, then i won't need to worry about table, queries and reports messed up correct? "Jerry Whittle" wrote: What are your concerns? If all the users can have access to the data, but non-users shouldn't, then password protecting the FE and BE could be good enough. However if you only want the users to see some of the data; or be able to only enter or edit records, but not delete (for example); or messing with the design of the tables orqueries, then you need to implement User Level Security or you could just password protect the BE and not tell the users. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Chantel33" wrote: I have created, split my database, but have concerns about security on the be, I have made the FE (mde) to place on each user's pc but i am wondering is it necessary for me to create user accounts? |
Thread Tools | |
Display Modes | |
|
|