RE: Security on a Database

Thank you very much. Yes, upon reading some of these threads I realised that
security is not so simple. I will do as you've suggested and thank you very
much for your response.

:)
Angeline

"jl5000" wrote:

> The security topic is not small, I suggest you read the help file, but just
> to point you where to start:
>
> a. Use the "User-Level Security Wizard" located in Tools/Security menu.
>
> and for
> b. If you your client has Access, simply send the database, security file,
> and a shortcut (the security topics in Access help have more detail) in a CD
> or via e-mail in a zipped file, if the client does not have access and you
> want to distribute more applications in the future, I will recommend you buy
> the Developer extensions for Microsoft office if you are using Access 2003,
> they have a packaging wizard that helps distribute applications with their
> own setup,
>
> --
> jl5000
> <a href="http://www.joshdev.com";></a>
>
>
> "Angeline" wrote:
>
> > Hi,
> > I work independently but I am currently buiding a database to capture staff
> > exit interviews for a Corporate Client. I am a bit of a novice in ACCESS but
> > have been able to build queries and forms to meet all the needs of the
> > program.
> >
> > Whilst I built it for myself, to be able to calculate patterns and trends of
> > dissatisfaction among staff - they (The Client) have requested to view all
> > the interviews which can be viewed from a form which has about 10 page tabs.
> >
> > Rather than send them the main table which the form points to, I would
> > prefer to send them the database but only allow them to view one form within
> > it.
> >
> > Can someone help me with :
> > a: How I program the database to secure everything else from being viewed
> > excpet this form. The form already has open on activate database built into
> > it but I want to be able to prevent them from going anywhere else.
> >
> > b: How can I package up the database so that I can send it across to them
> > and of course they would require to have ACCESS on their site.
> >
> > Hope someone can help. Many Thanks!
> > Angeline
.

Relevant Pages

  • Re: Access 2003 Macro Security Modification
    ... the desired way to prevent the macro security warning is to ... digitally sign your database. ... Your database fileon the client computer. ...
    (microsoft.public.access.modulesdaovba)
  • 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)
  • Re: access 2003
    ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
    (microsoft.public.access.conversion)
  • Re: Security ideas for n-tier?
    ... that have the same signature as stored procedures in the database. ... COM+ security allows you to configure role-based security down to the ... This moves authentication ... client into three layers, a thin client, a middle tier ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: access 2003
    ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
    (microsoft.public.access.conversion)