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

Protect Back-End Tables in Desktop Db - How?

P: n/a
Hi.

I have been working on an Access Db for awhile and am very close to
being ready to hand it over to the person who requested it. There will
be one user and the db will reside on a desktop PC.

Here's my dillemma? How do I insure that the user will not have access
to the tables? I'd hate for her to get curious and go in and "muck
around" with the data. I have the db split and have logic to disable
the "shiftkey bypass" on open. I plan to, also, convert the front-end
mdb to a front-end mde. However, what do I do with the back-end
(tables)? Is there a way to protect them?

I would like to keep the db split (front-end/back-end) so if
modifications are required in the future (to the
screens/reports/processing), I can just send a new front-end (I have the
'relink' logic in place on initial launching of application).

Any ideas for protecting the tables?

Thanks.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
SueB wrote:
Hi.

I have been working on an Access Db for awhile and am very close to
being ready to hand it over to the person who requested it. There
will be one user and the db will reside on a desktop PC.

Here's my dillemma? How do I insure that the user will not have
access to the tables? I'd hate for her to get curious and go in and
"muck around" with the data. I have the db split and have logic to
disable the "shiftkey bypass" on open. I plan to, also, convert the
front-end mdb to a front-end mde. However, what do I do with the
back-end (tables)? Is there a way to protect them?

I would like to keep the db split (front-end/back-end) so if
modifications are required in the future (to the
screens/reports/processing), I can just send a new front-end (I have
the 'relink' logic in place on initial launching of application).

Any ideas for protecting the tables?


Access has User Level Security (fairly advanced topic) that would be the
surest method. Otherwise you just use varying levels of obfuscation. For
example, your BE file could be placed anywhere and given any name. The
extension doesn't even have to be "MDB". That might make it hard for the
user to even know what file to look at.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

P: n/a
I just put a simply little "autoexec" macro that runs in the back end..

I have that macro launch a msgbox command that says you don't have
permissions. The user clicks ok, and they are kicked out.

works 99% of the time, and take no more time then it does to write this
post...

and, if you disable the shift key by-pass, then it not locked up tight, but
does keep the average access user out....
So, I make a macro called AutoExec. In the macro, I put the following code:

Action Parms
Msgbox message:You do not have permissions to run this file
Beep: Yes
Type: Critical
Title: Can not run

Quit: Options:Exit

Note that the "critical" setting seems to make the msgbox look much more
official!!!
As an alterative, you an make a nice little form in the back end, and set
the startup options to run that form that displays a message, and then when
they click ok...you do a application.quit.

And, to disable the "shift key", simply grab my shift key utility here to
turn off the shift key by-pass

http://www.members.shaw.ca/AlbertKal.../msaccess.html
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #3

P: n/a
Albert,

Thank you so much for your suggestions. I'll be looking to incorporate
them shortly. And I must send a very big thank you for your Mail merge
routines. I was referred to your website for sample routines from
someone in this very forum. The Mail Merge works like a charm. I was
thrilled with the results.

Regards,
SueB

*** Sent via Developersdex http://www.developersdex.com ***
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.