Any way to prevent links to my tables?

[Judy Ward]

I have an Access database with many users. I have not implemented security
and I do not use a back end/front end (for many reasons). I do have code to
kick users out of the database so that I can make code changes and compact
and repair the database. This has worked great for years. Now I have a user
who has decided to make his own Access database and link to some of my
tables. This is causing me problems when I need exclusive access to my
database. Is there any way I can prevent a user from linking to my tables?

Thank you,
Judy

 

[Stefan Hoffmann]

hi Judy,

Is there any way I can prevent a user from linking to my tables?

No, not really.

Explain your good reasons for not splitting your application to that
user. And prohibit this linking practice.


mfG
--> stefan <--

 

[Stefan Hoffmann]

hi Judy,

Is there any way I can prevent a user from linking to my tables?

No, not really.

Explain your good reasons for not splitting your application to that
user. And prohibit this linking practice.


mfG
--> stefan <--

 

[Jeff Boyce]

Judy

When you need exclusive access, I understand it is so you can "make code
changes".

Splitting your application to have data in a back-end and your front-end on
your PC would allow you to make code changes without needing to kick out the
users.

Perhaps if you advised the rogue linker that you were informing all the
current users that they had to suffer poorer response time because you were
unable to have exclusive access to the back-end data (hint, hint, wink,
wink, nudge, nudge)...?

Peer pressure can be a wonderful thing ...!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jeff Boyce]

Judy

When you need exclusive access, I understand it is so you can "make code
changes".

Splitting your application to have data in a back-end and your front-end on
your PC would allow you to make code changes without needing to kick out the
users.

Perhaps if you advised the rogue linker that you were informing all the
current users that they had to suffer poorer response time because you were
unable to have exclusive access to the back-end data (hint, hint, wink,
wink, nudge, nudge)...?

Peer pressure can be a wonderful thing ...!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[tina]

well, i can't think of a good business or technical reason for *not*
splitting a multi-user database. and in this case, i think doing so could
solve your issue of preventing unauthorized table links. you can split the
tables out to a backend db, and put a password on that db. move everything
else into a frontend db, and link to the password-protected backend tables.
you can use a variety of methods to "lock" the frontend db and prevent
direct access to the table links, then give each user a copy of the frontend
db. now nobody can link directly to the backend tables from another Access
db, without the password. and your users still have unrestricted use of the
frontend db that you provided to them.

bear in mind that a determined user/developer can find ways around, or ways
to undo, probably just about anything you do to lock your frontend - and get
to the linked tables that way. maybe you should sit down with this
particular user and discuss why he/she needs access to the table data, and
the problems it causes, and come up with a compromise solution that works
for both of you.

hth

 

[tina]

well, i can't think of a good business or technical reason for *not*
splitting a multi-user database. and in this case, i think doing so could
solve your issue of preventing unauthorized table links. you can split the
tables out to a backend db, and put a password on that db. move everything
else into a frontend db, and link to the password-protected backend tables.
you can use a variety of methods to "lock" the frontend db and prevent
direct access to the table links, then give each user a copy of the frontend
db. now nobody can link directly to the backend tables from another Access
db, without the password. and your users still have unrestricted use of the
frontend db that you provided to them.

bear in mind that a determined user/developer can find ways around, or ways
to undo, probably just about anything you do to lock your frontend - and get
to the linked tables that way. maybe you should sit down with this
particular user and discuss why he/she needs access to the table data, and
the problems it causes, and come up with a compromise solution that works
for both of you.

hth