User security advice

3 Jul 2009 4:37 AM

HKKS

What would be an efficient way to allow everyone to access our database
without ever having the option to modify it in any way, i.e. coding or
design? I will be the ONLY one who can get into the workings of it and modify
it. Users should not need a password, but I do. I've been having a varied
degree of success so far.

When it comes to security, I'd like to run it by an expert.

Thanks very much for your help.

--
HKKS
Tokyo, Japan

3 Jul 2009 8:33 AM

Keith Wilby

Show quote Hide quote

"HKKS" <H***@discussions.microsoft.com> wrote in message
news:F6F570F5-8C63-4E4E-895B-EAC95D53D3FD@microsoft.com...
>
> What would be an efficient way to allow everyone to access our database
> without ever having the option to modify it in any way, i.e. coding or
> design? I will be the ONLY one who can get into the workings of it and
> modify
> it. Users should not need a password, but I do. I've been having a varied
> degree of success so far.
>
> When it comes to security, I'd like to run it by an expert.
>
> Thanks very much for your help.
> --
> HKKS
> Tokyo, Japan

If you're using the mdb file format then you can use the built-in user-level
security. The down side is that it has a steep learning curve and many
pitfalls for the inexperienced. The starting point is the FAQ from MS,
there's a link to it on my web site along with a practical example. You'd
need to follow all of the steps in the order stated and omit nothing, even
if it seems trivial.

Either WORK ON A COPY of you files or BACK THEM UP before you try to apply
security because it's too easy to lock yourself out.

Keith.
www.keithwilby.co.uk

7 Jul 2009 5:41 AM

HKKS

Thanks Keith, I'll have a look on your site and walk through your
instructions carefully. I assume that this works on the mdE file that I
create from the mdB file. Please let me know otherwise.

--
HKKS
Tokyo, Japan

Show quoteHide quote

"Keith Wilby" wrote:

> "HKKS" <H***@discussions.microsoft.com> wrote in message
> news:F6F570F5-8C63-4E4E-895B-EAC95D53D3FD@microsoft.com...
> >
> > What would be an efficient way to allow everyone to access our database
> > without ever having the option to modify it in any way, i.e. coding or
> > design? I will be the ONLY one who can get into the workings of it and
> > modify
> > it. Users should not need a password, but I do. I've been having a varied
> > degree of success so far.
> >
> > When it comes to security, I'd like to run it by an expert.
> >
> > Thanks very much for your help.
> > --
> > HKKS
> > Tokyo, Japan
>
> If you're using the mdb file format then you can use the built-in user-level
> security. The down side is that it has a steep learning curve and many
> pitfalls for the inexperienced. The starting point is the FAQ from MS,
> there's a link to it on my web site along with a practical example. You'd
> need to follow all of the steps in the order stated and omit nothing, even
> if it seems trivial.
>
> Either WORK ON A COPY of you files or BACK THEM UP before you try to apply
> security because it's too easy to lock yourself out.
>
> Keith.
> www.keithwilby.co.uk
>
>

7 Jul 2009 8:19 AM

Keith Wilby

"HKKS" <H***@discussions.microsoft.com> wrote in message
news:2AA325CD-2220-469E-999B-7ADA5FBDE3E6@microsoft.com...
> Thanks Keith, I'll have a look on your site and walk through your
> instructions carefully. I assume that this works on the mdE file that I
> create from the mdB file. Please let me know otherwise.
>

In my experience, creating the mde is the penultimate process, the last
being to disable the bypass key. Remember also that my example is no
substitute for the FAQ!

Keith.
www.keithwilby.co.uk