Re: backend security - One field unchangeable

Tech-Archive recommends: Speed Up your PC by fixing your registry



"dave k" <davek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5938D947-4E73-496F-A4CD-C2C550F9CF83@xxxxxxxxxxxxxxxx
>I would like to make the a field in the back-end of a database unchangeable
> but keep the rest of the information modifiable. To simplify I don't mind
> people using the backend in any way they want I just want to set a field
> "Company Name" so that it is hard coded by me and cannot be changed. The
> database I am writing depends heavily on reports that all use this field
> in
> the heading (my security from unauthorized copies). I could put it in a
> table or in a module hard coded. Is there a way to keep it unchangeable?
> Currently there is no security (which I prefer) and the front-end is
> distributated as an MDE.
>
User level security is object based (forms, tables, etc). I'm not aware of a
method to achieve your objective at field level. You could use a text box
on a form to do it but this would mean setting up security.

Regards,
Keith.
www.keithwilby.com


.



Relevant Pages

  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • backend security - One field unchangeable
    ... I would like to make the a field in the back-end of a database unchangeable ... To simplify I don't mind ... the heading. ... Currently there is no security and the front-end is ...
    (microsoft.public.access.security)
  • Re: Create a Form Password
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down ... into two big categories: home-grown security or Access ... User Level Security is using ...
    (microsoft.public.access.forms)
  • Re: setting a password on a button on the switchboard
    ... Let me provide my *few* thoughts about Access Security. ... Security in an Access database can probably be broken down into two big categories: ... User Level Security. ... What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: A2K Splitting and Security
    ... to the user's log-in name which would map him/her to a security level. ... on a query that used the underlying table in the BE database. ... > You don't really need user level security if you don't care about assigning ... >> incorporate the idea of the complied mde type file. ...
    (microsoft.public.access.tablesdbdesign)