I am new to the community, so please let me know if I am following proper
etiquette.

I am working wth Access 2003 and am developing a database so managers can
submit salary increase recommendations. I plan to have one table of employee
information including salaries, who the employee reports to (manager), and a
blank field in which a manager can input a suggested increase. I then plan
to create a query and a form so that a manager can only see his/her
employees. I realize I will have to implement user level security. And each
manager will be a user.

What I would like to do is create one query and one form and have the
records a manager sees depend on the user they log in as. I am envisioning
the user ID as a field in the table with employee data, but how do I get the
query/form to restrict the records based on which user logs in?

I also want to limit managers to only inputting a recommended salary
increase amount - they should not be able to edit other fields.

Thank you for your time!

Edward Whitmore

Hi Edward,
here is a website where you can download a sample database called
UserSeesOnlyHisRecords.mdb (beginner)
http://www.rogersaccesslibrary.com/f...ts.asp?TID=220



Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"Edward_Whitmore" <(E-Mail Removed)> wrote in
message news:B675BF91-3D53-476A-B5A3-(E-Mail Removed)...
>I am new to the community, so please let me know if I am following proper
> etiquette.
>
> I am working wth Access 2003 and am developing a database so managers can
> submit salary increase recommendations. I plan to have one table of
> employee
> information including salaries, who the employee reports to (manager), and
> a
> blank field in which a manager can input a suggested increase. I then
> plan
> to create a query and a form so that a manager can only see his/her
> employees. I realize I will have to implement user level security. And
> each
> manager will be a user.
>
> What I would like to do is create one query and one form and have the
> records a manager sees depend on the user they log in as. I am
> envisioning
> the user ID as a field in the table with employee data, but how do I get
> the
> query/form to restrict the records based on which user logs in?
>
> I also want to limit managers to only inputting a recommended salary
> increase amount - they should not be able to edit other fields.
>
> Thank you for your time!
>
> Edward Whitmore
>
>
>

"Jeanette Cunningham" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Edward,
> here is a website where you can download a sample database called
> UserSeesOnlyHisRecords.mdb (beginner)
> http://www.rogersaccesslibrary.com/f...ts.asp?TID=220
>
>

You may also want to consider disabling the AllowBypassKey property
depending on how Access "savvy" your users are.

Keith.
www.keithwilby.com

Dear Jeanette:
Thank you very much for responding to my question - and for doing so so
promptly. I went to the website and downloaded the information and I think
it will do exactly what I want. I was a bit intimidated by the "beginner"
label - if this is beginning, I have a LONG way to go.

Regards,

Edward Whitmore

"Jeanette Cunningham" wrote:

> Hi Edward,
> here is a website where you can download a sample database called
> UserSeesOnlyHisRecords.mdb (beginner)
> http://www.rogersaccesslibrary.com/f...ts.asp?TID=220
>
>
>
> Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia
>
>
> "Edward_Whitmore" <(E-Mail Removed)> wrote in
> message news:B675BF91-3D53-476A-B5A3-(E-Mail Removed)...
> >I am new to the community, so please let me know if I am following proper
> > etiquette.
> >
> > I am working wth Access 2003 and am developing a database so managers can
> > submit salary increase recommendations. I plan to have one table of
> > employee
> > information including salaries, who the employee reports to (manager), and
> > a
> > blank field in which a manager can input a suggested increase. I then
> > plan
> > to create a query and a form so that a manager can only see his/her
> > employees. I realize I will have to implement user level security. And
> > each
> > manager will be a user.
> >
> > What I would like to do is create one query and one form and have the
> > records a manager sees depend on the user they log in as. I am
> > envisioning
> > the user ID as a field in the table with employee data, but how do I get
> > the
> > query/form to restrict the records based on which user logs in?
> >
> > I also want to limit managers to only inputting a recommended salary
> > increase amount - they should not be able to edit other fields.
> >
> > Thank you for your time!
> >
> > Edward Whitmore
> >
> >
> >
>
>
>

Dear Keith:
Thank you very much for replying to my question. I am pretty confident my
users are not too savvy - but disabling that property sounds like a good idea
to me. I am new at the whole security business and prefer transparency, but
compensation is very emotional information and keeping it confidential is
pretty important.

Regards,

Edward Whitmore

"Keith Wilby" wrote:

> "Jeanette Cunningham" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Hi Edward,
> > here is a website where you can download a sample database called
> > UserSeesOnlyHisRecords.mdb (beginner)
> > http://www.rogersaccesslibrary.com/f...ts.asp?TID=220
> >
> >
>
> You may also want to consider disabling the AllowBypassKey property
> depending on how Access "savvy" your users are.
>
> Keith.
> www.keithwilby.com
>
>

Edward_Whitmore <(E-Mail Removed)> wrote:

>Thank you very much for replying to my question. I am pretty confident my
>users are not too savvy - but disabling that property sounds like a good idea
>to me. I am new at the whole security business and prefer transparency, but
>compensation is very emotional information and keeping it confidential is
>pretty important.

In which case the data should be kept in SQL Server or other database.
The problem is that anyone can find the data MDB on the server, copy
it to a thumb drive, take it home and browse the tables on thier copy
of Access.

You can not depend on someone being ignorant as they may know other
people who know Access. And indeed those other people may be reading
this posting. <smile>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Dear Keith:
After a brief look around, I realize that I don't know what the
AllowBypassKey property is or where I find it or what it does.
Would you be able to help?
Thanks

Edward_Whitmore

"Edward_Whitmore" wrote:

> Dear Keith:
> Thank you very much for replying to my question. I am pretty confident my
> users are not too savvy - but disabling that property sounds like a good idea
> to me. I am new at the whole security business and prefer transparency, but
> compensation is very emotional information and keeping it confidential is
> pretty important.
>
> Regards,
>
> Edward Whitmore
>
> "Keith Wilby" wrote:
>
> > "Jeanette Cunningham" <(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> > > Hi Edward,
> > > here is a website where you can download a sample database called
> > > UserSeesOnlyHisRecords.mdb (beginner)
> > > http://www.rogersaccesslibrary.com/f...ts.asp?TID=220
> > >
> > >
> >
> > You may also want to consider disabling the AllowBypassKey property
> > depending on how Access "savvy" your users are.
> >
> > Keith.
> > www.keithwilby.com
> >
> >