Re: URGENT HELP PLEASE - stopping someone importing my queries
From: Annette (Annette_at_discussions.microsoft.com)
Date: 10/24/04
- Next message: Vince Lambert: "Convert access color to hexadecimal"
- Previous message: Annette: "URGENT HELP PLEASE - stopping someone importing my queries"
- Maybe in reply to: Annette: "URGENT HELP PLEASE - stopping someone importing my queries"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 23 Oct 2004 21:25:01 -0700
Thank you so very much, it confirmed a full weeks of work with user level
security, thank you again. I am fairly new to this, but will try to play
with the hiding queries, had not thought of that, but not sure what you meant
by "having them call functions of my own design"
Again thank you very much.
"Chris Mills" wrote:
> I hate to tell you this, but even if you implement user-level security
> properly, it does not prevent a Query design being read. Because, a user needs
> read-design permissions in order to have read-data permissions. In some cases
> you can hide the query by placing it in a form's Record Source, or in other
> cases you may be able to place a query in code and execute it from code.
>
> If your queries contain design secrets, you may be able to partially hide what
> they do by having them call functions of your own design.
>
> MDE is your most secure bet, but as you say does not protect queries. But
> surely queries are used in the execution of forms, reports, etc, where they
> can be hidden and not presented as stored Queries. I would have thought that
> mde with AllowBypassKeys disabled would be "reasonably secure". But you simply
> cannot stop an Access expert of sufficient expertese.
>
> Also, it is virtually impossible to prevent data being copied, for the same
> reason that the user needs read permissions. I have experimented with encoding
> data, which sorta works but computer experts would probably have little
> difficulty with.
>
> > Also I found that by stopping all the Users permission they can't get into
> > the database at all.
> You are supposed to create your own "users" group(s) with appropriate
> permissions, called something else of course, and join them to that. None of
> the default users or groups should have any permissions at all.
>
> Chris
>
> "Annette" <Annette@discussions.microsoft.com> wrote in message
> news:57C75AB0-830A-46CA-895E-90C999B30015@microsoft.com...
> > Hi,
> >
> > I've written an Access database using XP, but converting it to 2000 so my
> > collegues can use it on older MS versions, and while i want users to add
> data
> > to it I don't want them accessing Forms, Queries and reports in Design View.
> >
> > I've secured the main switchboard by creating a module that stops bypassing
> > by using the Shift key on entry. My problem lies in that anyone can open a
> > new database, copy my original using File Import and then has access to my
> > queries. etc.
> >
> > I'ver followed the suggestions on both Jack Macdonalds and Joan Wilds
> > brillaint web pages but in my frustration must have missed some steps. I
> > have changed ownership of every thing to my "Super User" and tried numerous
> > attempts at different permissions
> >
> > Also I found that by stopping all the Users permission they can't get into
> > the database at all.
> >
> > I've looked at MDE files (allbeit fleetingly) but can still import them into
> > a new database and have total access. But with MDe you can still import
> > queries. The queries took ages and I dont want to give them away to
> > competitors
> >
> > Any help would be really appreciated
> >
> > thanks
> >
> > Annette
> >
>
>
>
- Next message: Vince Lambert: "Convert access color to hexadecimal"
- Previous message: Annette: "URGENT HELP PLEASE - stopping someone importing my queries"
- Maybe in reply to: Annette: "URGENT HELP PLEASE - stopping someone importing my queries"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
