Securing BE content without a Workgroup

  • Thread starter Thread starter Chantel33
  • Start date Start date
C

Chantel33

I currently have a split database and have deployed a FE(mde) on individual
team members computers, although they can not make changes to the design,
they can still make changes to others entries. How can i limit the data they
view to only their data and not other users. Each team member currently has
an Operation ID and I have field in the queries an tables.
 
 
Arvin can you provide some of the other ways, my main concern is that each
user is only able to edit their own entry. I don't have access to the
msaccess.exe file, creating user level security and a workgroup would involve
getting our IT dept involved or how long this will take, so if you could
provide some of the milder ways i would appreciate it.

Thank you
 
Everyone running the database has access to msaccess.exe or you cannot open
a database. The only exception is on a Terminal Server. You don't need to
get IT involved.

That said, the following will not secure the tables, so if you users can see
them, it won't work. First hide the database window, so they cannot see the
tables or create queries. That can be by-passed, so you can use code to stop
that:

http://www.mvps.org/access/general/gen0040.htm

Now you need a function to identify the user:

http://www.mvps.org/access/api/api0008.htm

Add a column to each table, and the corresponding forms to identify each
user by the Network UserName, then use the function in each query:

SELECT tblMyData.*
FROM tblMyData
WHERE (((tblMyData.UserName)=fOSUserName()));
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
 
I am a begginer with access and have little knowledge of coding, therefore i
do not know where to began with the Allowbypass, however i understand the
section portion of it "identify user" and creating the query. The database
is split and the BE is in a secured network folder, if i use the second
portion:
Now you need a function to identify the user:

http://www.mvps.org/access/api/api0008.htm

Add a column to each table, and the corresponding forms to identify each
user by the Network UserName, then use the function in each query:

SELECT tblMyData.*
FROM tblMyData
WHERE (((tblMyData.UserName)=fOSUserName()));
Click to expand...

will this limit the users to their data only! This is my main concern! I
have unchecked the navigation bar so it doesn't display, and removed most
access on the startup menu. and each FE database made to an MDE. I have a
filter on my form to show the opid info of the user, but that can easily be
removed, thus me needed an addition security.
 
Back
Top