Re: limiting table access and RWOP queries

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

thanks again Chris,
-I'm assuming that non of my users will have the skill or motivation to
break in to the data on purpose. I just don't want them to be able to do it
accidently.I just want to figure out the best way to keep the average user
from changing data other than through my forms, or from getting lost
somewhere they don't understand.
I think next time I'll wrap all my main tables in RWOP queries, then it
looks like I can write sql in code based on these queries. But for now,
hiding the database window, allowbypass keys, and custom menus is probably
what I'll do. Once you turn off AllowBypassKeys, is it completely locked and
you have to keep a separate copy that you can get into, or is there some way
in code to get into it as an admin?


"Chris Mills" <phad_nospam@xxxxxxxxxxxxxx> wrote in message
news:uTSHSA3tFHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
>> I want to completely lock users out of the tables, so that they can't
>> edit,
>> delete, etc except through forms. I'm not so interested in limiting the
>> fields they can see, I just want to make sure all their access to data is
>> through forms.
>>
> We would all like to do that. I can't.
>
> You'll be aware that is impossible in Microsoft Access (and any Personal
> Database System so far as I know) to lock IT-knowledgable users out.
>
> That said, you can fairly-well lock-down Access for average users (as
> against
> Access Gurus).
>
> Removing Database Window, AllowBypassKeys, Default Menus, are fundamental
> to
> limiting the average user. As important as User-Level Security, which is a
> requirement too.
>
> But you cannot prevent data being copied-out (IMHO) unless you encrypt it
> somehow, for the simple reason that by definition you have decided to give
> them access to the data. You can make it harder to bulk-copy by disabling
> datasheet view, keyboard select all/copy, default menus, and things like
> that.
> Harder, not impossible.
> (much like the things Runtime disables, though Runtime is not of itself a
> security measure)
>
> Your statement still doesn't help much (ultimately it's impossible). It
> might
> be more helpfull if you identified the threat (and likelihood). It has
> been
> stated (and my experience agrees) that the majority of users just want the
> software to do their jobs or make their jobs easier. They are happy to pay
> including for service. This is related to whether they want to usurp your
> program, rather than recover nuclear secrets, of course.
>
> (One reason for security is solely economic. What percentage of sales am I
> likely to lose from hacking, and how much effort should I spend?)
>
> Chris
>
> (Your requirement is impossible without more info on reasons)
>
>
>


.

Relevant Pages

  • Re: Automate Post
    ... The reason for this is because as ... but security does have it's occasional drawbacks. ... Regards, Chris. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Is there how to client open file in your PC using ASP component??
    ... "Chris Barber" escreveu na mensagem ... > Vilmar Brazão de Oliveira ... >>> Security, security, security. ...
    (microsoft.public.inetserver.asp.components)
  • Re: ATWT - CASTING NEWS
    ... all recurring meant was that if the show wanted you and you were ... I think that in DB's case, they never intended on keeping Chris ... whatever reason it's simply not worth it to you. ... but the writing didn't help. ...
    (rec.arts.tv.soaps.cbs)
  • Re: Cross your fingers, cross your toes ...
    ... how did the job interview go? ... But the reason they didn't want me was ... I didn't see the original London Chris posting his pictures (but maybe I ...
    (soc.motss)
  • Re: Cross your fingers, cross your toes ...
    ... how did the job interview go? ... But the reason they didn't want me was ... To summarise: Chris H ... Chris "Nice pictures" Hansen ...
    (soc.motss)