backend security question

[Guest]

This is not the typical how do I secure the backend with user level, I
already have that done and frontend, etc. I was just wondering if anyone has
have disabled the shift on the backend? I know silly question.

The reason I ask is because the backend is on a shared drive, which has to
be accessible for people to use. I have all tables secured for who can view
them, but there is one everyone has access to, which is the employee table.
My only concern is that if someone were to open the backend and view that
table, it has everyone's SS#'s, although most people who have access already
have access to that information, there are a few who do not.

One solution would be just to separate that out on it's own table and secure
that table, but I was wondering if anyone had ever just turned off the
startup and disabled the shift to the backend, making a copy before of
course? I didn't know how that would work since that data always changed but
you could import the tables into your shift enabled if you had to make
changes to the tables.

 

[Joan Wild]

The reason I ask is because the backend is on a shared drive, which
has to be accessible for people to use. I have all tables secured
for who can view them, but there is one everyone has access to, which
is the employee table. My only concern is that if someone were to
open the backend and view that table, it has everyone's SS#'s,
although most people who have access already have access to that
information, there are a few who do not.

You could deny all permissions on the tables, and use RWOP (run with owner
permissions) queries for all data interaction.

One solution would be just to separate that out on it's own table and
secure that table, but I was wondering if anyone had ever just turned
off the startup and disabled the shift to the backend, making a copy
before of course?

You certainly could do that (no need to make a copy though).

I didn't know how that would work since that data
always changed but you could import the tables into your shift
enabled if you had to make changes to the tables.

You can enable the shiftkey from another database. Importing wouldn't be a
good idea as the permissions won't come with the table.

 

[Guest]

Thanks. I have thought about using RWOP, and actually have all the queries
set up that way so they can access parts of the other tables. The only
reason I never did that on the Employee Table, main reason, didn't really
think about there being anything there that wasn't somewhere else, and since
I thought that, I have numerous forms with combo boxes that allow users to
choose the employee name which is linked to that table. Combo boxes use SQL
to limit them, could you put run with owner access on those and then disable
the table?? That would save me from having to switch all those to a query,
or separating out a table.

How do you activate the shift from another database? Do you just enter the
name of the Database into the ChangeProperty statement?

 

[Joan Wild]

Combo boxes use SQL to limit them, could you
put run with owner access on those and then disable the table?? That
would save me from having to switch all those to a query, or
separating out a table.

No you can't just add the WITH OWNERACCESS OPTION to the SQL statement.
That won't work because the owner in this case is the user running the SQL
statement. You have to create a saved query with RWOP applied and use that
as the rowsource for the combo.

How do you activate the shift from another database? Do you just
enter the name of the Database into the ChangeProperty statement?

If you look at code you'll see
Set db = Currentdb()

You have to modify this to point to the other database
Dim wrk As Workspace
Set wrk = DBEngine.Workspaces(0)
Set db = wrk.OpenDatabase("C:\Program Files\Good Works\gw1997.mdb")