Re: hide SOME query results for unauthorized users

Tech-Archive recommends: Fix windows errors by optimizing your registry


Thanks.

Ok, I know how to make a table. I know how to assign a password to a
database to make it impossible to open without the password. What I'm
confused about is how to set-up a "login" procedure. Is it done via a
switchboard or something?

"June7 via AccessMonster.com" wrote:

Building tables is the easy part. Use the table designer tool. Define fields
you desire (name, data type, etc.) Possible fields for Users table: LastName,
FirstName, Title, Department, SecurityLevel, PhExt.

The tricky part comes in controlling user access. You want them to be able to
create their own queries. If you let them use the toolbar tools then you
might have no control. I have a form in my project that has comboboxes from
which the users can select criteria (date range, document number, etc). Then
with VBA code I compile a SQL SELECT statement or set form Filter properties
(depending on the criteria selected) that will execute the users request. The
toolbars are not available to users. They are totally at my mercy -
bwahahahaha! The form RecordSource as well as these combobox lists of
choices can limited based on the user login ID.

Not having a specific issue to solve, can't offer any more than to say it can
be done. You will learn a lot by doing, so dive in and when you have specific
issue, post a question.

Derek wrote:
Thank you for the response. To answer your questions; my DB is not created
yet, I am still in the planning stage so I don't have anything constructed.
When I do have tables, one of the columns will be a checkbox for any user
(but typically only the users who are generating the sensitive data) to flag
the record as sensitive. Sure, you can hide from everyone all records in a
query that are flagged by splitting the database and excluding all but a few
from the back-end. But if I want everyone to be able to create their own
queries how do I allow some but not all users to see the flagged records.

The users table you mention sounds interesting - but I have no idea how to
create one.

I presume you have some kind of login procedure, perhaps even with password
protection, and you have a table of Users and Login info. Include the tag
[quoted text clipped - 8 lines]
a record as being available to permission holders, but how can I keep the
data in the record from being viewed by users without that permission?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-queries/200906/1


.

Relevant Pages

  • Re: PDO: Switch database user without reopening connection
    ... At the bare minimum there will be a login user who only has ... modifications to the database as well (editors get update permission, ... As database connections are expensive to ... a certain visitor in the Session, and use that value to start the right ...
    (comp.lang.php)
  • Re: PDO: Switch database user without reopening connection
    ... At the bare minimum there will be a login user who only has ... the postgres user they are logged in as to one that can make ... modifications to the database as well (editors get update permission, ... As database connections are expensive to ...
    (comp.lang.php)
  • RE: How to allow users to change their password?
    ... be set up to provide the Security dialog window for password changes. ... I'll have to login using their login ... > name/password first. ... See http://www.QBuilt.com for all your database needs. ...
    (microsoft.public.access.security)
  • Re: Please! Doesnt anyone know a better way to do this?
    ... account, they need to automatically be directed to the page to enter data ... session variable on the Account page. ... I assume here that you're checking a database when the user attempts to ... When a new user attempts to login or clicks to register, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Enter user name, enter password, then press enter...
    ... What do you do when the customer asks that the database login in be the same ... username and password to use all of the stuff that she is permitted to use. ... I have implemented this type of security for Access, VB, and Web Based ASP ...
    (microsoft.public.access.forms)