allow updates by user

[Patty]

Hello All-

I have a form with lots of tabs and fields which currently allows everyone
to update all fields. Security is not being used. Now I need to allow
certain users to update all fields and the others be read only. I have a
table of users by network logon and I use the userid in my application. I've
added an "updater" field in my user table.

I've never used Access security and am hoping to avoid it unless there's a
strong case for it.

My general question is: should I use security or code?

If code can I control it at the form level? If so, how?

If someone can point me in the right direction, I can figure out the
details.

TIA

PB

 

[Rick Brandt]

Hello All-

I have a form with lots of tabs and fields which currently allows
everyone to update all fields. Security is not being used. Now I
need to allow certain users to update all fields and the others be
read only. I have a table of users by network logon and I use the
userid in my application. I've added an "updater" field in my user
table.

I've never used Access security and am hoping to avoid it unless
there's a strong case for it.

My general question is: should I use security or code?

If code can I control it at the form level? If so, how?

If someone can point me in the right direction, I can figure out the
details.

If you are just trying to provide guidance to cooperative users then coding
against your user table is fine.

If you are trying to have strict control over clerical users who are not
familiar with Access then User Level Security is adequate.

If you need to deter knowledgable people who might also intentionally do
something malicious then your data should not be in an MDB file. Access
security is to easy to break.

 

[ucdcrush]

Hello All-

I have a form with lots of tabs and fields which currently allows everyone
to update all fields. Security is not being used. Now I need to allow
certain users to update all fields and the others be read only. I have a
table of users by network logon and I use the userid in my application. I've
added an "updater" field in my user table.

I've never used Access security and am hoping to avoid it unless there's a
strong case for it.

My general question is: should I use security or code?

If code can I control it at the form level? If so, how?

If someone can point me in the right direction, I can figure out the
details.

TIA

PB

Through code, you can just make a global variable for "updater" status
which is set when the person first logs in. Like make a basGlobal
module, and inside use:

Global updater As boolean

Then on the form load event, check basglobal.updater and if it's true,
unlock the controls linked to fields that can be edited.

 

[Patty]

Thank you for your help. I trust my users. I need to protect myself from
someone accidentally changing something when they only needed to look
something up.

When you say "unlock the controls linked to fields that can be edited." I
assume you mean each field gets enabled individually or is there something I
can do at the form level?