Group:  Microsoft Access ยป microsoft.public.access.security
Thread: Is it a good idea to create my own navigational buttons ??

DotNetBag
.NET Development Newsgroups

HTVi
TV Discussion Newsgroups

Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Rising Antivirus 2006

Is it a good idea to create my own navigational buttons ??
Wellie 01.08.2006 01:59:02
I have a new requirement to lock and unlock specify fields on the form such
that users can or cannot edit data field depending on the condition of other
fields. For example, if the record displayed is Approved by a supervisor
(indicated by the "Approved" field in the record, I'd like to LOCK the field
such that other users cannot modify the contents of certain fields. If it is
NOT approved, the user can still modify certain fields of the record

At present, I'm using the default Navigational Button at the bottom of the
form to allow users to browse the record.

Is it a good idea for me to disable the Navigation Button feature in the
form and then create my own set of Next Record, Previos Record, New Record,
etc buttons to brows the record such that I can enable/disable the field
based on the condition of one of the record field ? If so, can somone
provide me some guidance on how to do it ?

If it is not a good idea, can someone advise a method to achieve this
objective ?
Re: Is it a good idea to create my own navigational buttons ??
"Rick Brandt" <rickbrandt2[ at ]hotmail.com> 01.08.2006 02:12:29
Wellie wrote:
[Quoted Text]
> I have a new requirement to lock and unlock specify fields on the
> form such that users can or cannot edit data field depending on the
> condition of other fields. For example, if the record displayed is
> Approved by a supervisor (indicated by the "Approved" field in the
> record, I'd like to LOCK the field such that other users cannot
> modify the contents of certain fields. If it is NOT approved, the
> user can still modify certain fields of the record
>
> At present, I'm using the default Navigational Button at the bottom
> of the form to allow users to browse the record.
>
> Is it a good idea for me to disable the Navigation Button feature in
> the form and then create my own set of Next Record, Previos Record,
> New Record, etc buttons to brows the record such that I can
> enable/disable the field based on the condition of one of the record
> field ? If so, can somone provide me some guidance on how to do it ?
>
> If it is not a good idea, can someone advise a method to achieve this
> objective ?

There is a pefectly good event that is meant to be used for this. The Current
event of the form. Put your code there and it works no matter how the user
arrives at the record (and there are LOTS of ways besides the buttons at the
bottom).

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


Home | Search | Terms | Imprint | Contact
Newsgroups Reader - provided by WiredBox.Net