T
TomsLibrary
I have used the wizard to secure my database for use by higher level users,
but I wish to create limited user groups that
a) cannot “unhide" their underlying tables
b) can only use the database via the menu system created using the 2003 menu
system
c) can only perform selected functions (form use, report view/print) from
that menu system as defined in the security profile for that logged in user
category
d) cannot use menu functions beyond print, print preview and spell check
(for entries)
The application is in team-based training support. Employees
contribute/submit/critique knowledge content (available queried content
varies with position/progress within the training system. “Expertâ€
experienced staff evaluates and corrects submitted. Critiques by trainees of
content serves to both evaluate training quality/consistency/depth and, by
accepting suggestions for change and improvements in clarity, it builds
clarity and buy-in.
Currently, printouts and paper question/critique forms are used to serve the
limited access and critique interactive functions. The editors print updated
knowledge content reports, then screen and edit submissions and critiques
manually. I wish to apply security to allow direct viewing of
user-appropriate queried material (i.e. access allowed only to those queried
reports on the menu system that are appropriate to the security profile of
the logged user). I wish the same system to allow addition of new questions
and critiques via selected input forms (i.e., those queried forms released as
appropriate access for that secured user). Access’s wizard-based system
opens broader access by object. I am not clear as to how to define a
security group so that only selected queried reports and forms are accessible
(I.e., denying all direct or full access to underlying tables or queried.) I
am also not sure how to define security in a way that denies all access to
toolbar functions and hidden table viewing for these groups (without
disturbing the toolbar access of existing “editorsâ€.)
Existing groups are the database administrator (full access) and content
editors (full content permission, no design permissions). Planned limited
groups are various classes of trainees that would be able to access queried
forms and reports appropriate to their current level of training. All forms
appropriate for access are displayed in the menu system; the displayed forms
and reports that would be active would need to vary by user login.
but I wish to create limited user groups that
a) cannot “unhide" their underlying tables
b) can only use the database via the menu system created using the 2003 menu
system
c) can only perform selected functions (form use, report view/print) from
that menu system as defined in the security profile for that logged in user
category
d) cannot use menu functions beyond print, print preview and spell check
(for entries)
The application is in team-based training support. Employees
contribute/submit/critique knowledge content (available queried content
varies with position/progress within the training system. “Expertâ€
experienced staff evaluates and corrects submitted. Critiques by trainees of
content serves to both evaluate training quality/consistency/depth and, by
accepting suggestions for change and improvements in clarity, it builds
clarity and buy-in.
Currently, printouts and paper question/critique forms are used to serve the
limited access and critique interactive functions. The editors print updated
knowledge content reports, then screen and edit submissions and critiques
manually. I wish to apply security to allow direct viewing of
user-appropriate queried material (i.e. access allowed only to those queried
reports on the menu system that are appropriate to the security profile of
the logged user). I wish the same system to allow addition of new questions
and critiques via selected input forms (i.e., those queried forms released as
appropriate access for that secured user). Access’s wizard-based system
opens broader access by object. I am not clear as to how to define a
security group so that only selected queried reports and forms are accessible
(I.e., denying all direct or full access to underlying tables or queried.) I
am also not sure how to define security in a way that denies all access to
toolbar functions and hidden table viewing for these groups (without
disturbing the toolbar access of existing “editorsâ€.)
Existing groups are the database administrator (full access) and content
editors (full content permission, no design permissions). Planned limited
groups are various classes of trainees that would be able to access queried
forms and reports appropriate to their current level of training. All forms
appropriate for access are displayed in the menu system; the displayed forms
and reports that would be active would need to vary by user login.