By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,705 Members | 1,845 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,705 IT Pros & Developers. It's quick & easy.

Security - mdw or different interfaces?

P: n/a
Yes, I've downloaded and read the white paper (though some time ago).

I was considering an alternative to the built-in Access security. Having
more than one FE file. For instance there are a few maintenance forms (for
adding/editing a few lookup tables) which I only really want the office
administrator to have access to. Other forms I may want to be uneditable by
certain people etc. It may actually be simpler to just create a different FE
for 2 or 3 different categories of user. This is a small app, on a 10 user
network, split FE/BE. 3 of the users are doing, at the moment, all the data
entry and it will probably stay like that. Given that these users seem to
have no compunction about giving each other their NT logons, then I expect
they'll do the same with Access, if they need to. I've told them it's a bad
idea, but it's their office. So infact different FEs may be a better idea.
At least they'll have to walk to a different part of the building and get
onto someone else's machine if they want a different level of access.

I'm thinking of the downsides. Mainly that this could become messy to
distribute.

Any thoughts?

TIA, Mike MacSween
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
TC
The answer might depend on whether you want to stop them editing the tables
in the BE directly. If you do, Access security is the only apparent way to
go, no?

TC
"Mike MacSween" <mi******************@btinternet.com> wrote in message
news:3f*********************@pubnews.gradwell.net. ..
Yes, I've downloaded and read the white paper (though some time ago).

I was considering an alternative to the built-in Access security. Having
more than one FE file. For instance there are a few maintenance forms (for
adding/editing a few lookup tables) which I only really want the office
administrator to have access to. Other forms I may want to be uneditable by certain people etc. It may actually be simpler to just create a different FE for 2 or 3 different categories of user. This is a small app, on a 10 user
network, split FE/BE. 3 of the users are doing, at the moment, all the data entry and it will probably stay like that. Given that these users seem to
have no compunction about giving each other their NT logons, then I expect
they'll do the same with Access, if they need to. I've told them it's a bad idea, but it's their office. So infact different FEs may be a better idea.
At least they'll have to walk to a different part of the building and get
onto someone else's machine if they want a different level of access.

I'm thinking of the downsides. Mainly that this could become messy to
distribute.

Any thoughts?

TIA, Mike MacSween

Nov 12 '05 #2

P: n/a
> I was considering an alternative to the built-in Access security. Having
more than one FE file. For instance there are a few maintenance forms (for
adding/editing a few lookup tables) which I only really want the office
administrator to have access to. Other forms I may want to be uneditable by
certain people etc. It may actually be simpler to just create a different FE
for 2 or 3 different categories of user. This is a small app, on a 10 user
network, split FE/BE. 3 of the users are doing, at the moment, all the data
entry and it will probably stay like that. Given that these users seem to
have no compunction about giving each other their NT logons, then I expect
they'll do the same with Access, if they need to. I've told them it's a bad
idea, but it's their office. So infact different FEs may be a better idea.
At least they'll have to walk to a different part of the building and get
onto someone else's machine if they want a different level of access.

I'm thinking of the downsides. Mainly that this could become messy to
distribute.

Any thoughts?

TIA, Mike MacSween


I'd say that's fine--split up the forms into three separate "applets"
and install each as a separate shortcut. That way, you don't have to
mess with storing their permissions in a table of some sort, or
attempt to integrate it with JET security--just give them different
shortcuts for each of the three parts. If they want all three parts,
that's fine--they get all three plopped on their desktop. The worst
part of this is if they somehow figure out how the shortcuts work, but
that's unlikely, given that Windows cuts off the command-line in the
Shortcut properties box way before I get to the "/wrkgrp etc" part of
the command-line.

So as for deploying the database, just do three separate deployments.
Pete
Nov 12 '05 #3

P: n/a
"TC" <a@b.c.d> wrote in message news:1065000615.132478@teuthos...
The answer might depend on whether you want to stop them editing the tables in the BE directly. If you do, Access security is the only apparent way to
go, no?


At the moment all I want to do is stop users who hardly do any data entry,
and don't really have much to do with the application, inadvertantly editing
data, wrongly. It's a small family firm and I'm confident that there's
little chance of any malicious tampering.

Cheers, Mike MacSween


Nov 12 '05 #4

P: n/a
TC

Mike MacSween <mi******************@btinternet.com> wrote in message
news:3f*********************@pubnews.gradwell.net. ..
"TC" <a@b.c.d> wrote in message news:1065000615.132478@teuthos...
The answer might depend on whether you want to stop them editing the tables
in the BE directly. If you do, Access security is the only apparent way to go, no?


At the moment all I want to do is stop users who hardly do any data entry,
and don't really have much to do with the application, inadvertantly

editing data, wrongly. It's a small family firm and I'm confident that there's
little chance of any malicious tampering.

In that case I would imagine that user-level security is overkill, & your
idea of keeping the relevant programs physically seperate would be ok.

What about putting them in a small db on a diskette or CD? Then, the
relevent people could maintain physical control of that diskette or CD, only
passing it out when required, & getting it back asap. Then you can use the
relevant programs on *any* PC.

HTH,
TC
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.