Yes, it is technically feasible to disable the <Shift> bypass ... I don't
have first hand experience with it so we'll hope for a reader who does, or
you can search on-line for the code.
On the other hand, you might want to let the users know that 'if they break
it, they fix it!' <g>
Good luck!
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
"shm135" <(E-Mail Removed)> wrote in message
news:a021cb30-a48d-4ee6-8304-(E-Mail Removed)...
On Apr 8, 2:44 pm, "Jeff Boyce" <nonse...@nonsense.com> wrote:
> Sam
>
> Does this mean that you are giving your users access to the tables
> directly?
> That is, are you providing a user-interface that helps them get their jobs
> done, or are you forcing them to learn/know enough Access to get into
> trouble?<g>
>
> If you don't want folks looking at the tables, you could always hide them.
> First set up your queries against them, then hide them. Note that if you
> set your queries so that they provide read-only views of the data, the
> users
> won't be able to use the queries to modify the table data, just look.
>
> If you need more security than that, describe your situation a bit more...
>
> Regards
>
> Jeff Boyce
> Microsoft Access MVP
>
> --
> Disclaimer: This author may have received products and services mentioned
> in this post. Mention and/or description of a product or service herein
> does not constitute endorsement thereof.
>
> Any code or pseudocode included in this post is offered "as is", with no
> guarantee as to suitability.
>
> You can thank the FTC of the USA for making this disclaimer
> possible/necessary.
>
> "shm135" <shmou...@gmail.com> wrote in message
>
> news:51dba44f-891c-4a47-b63e-(E-Mail Removed)...
>
>
>
> > Hi,
>
> > I have a database which links to another database on the network. I
> > have linked 5 tables from database1 into database2. Users do not have
> > access to database2. Only I will have access.
>
> > Currently, users can not edit the design of the 5 tables, since they
> > are linked tables. However, they are able to open and view everything
> > in the tables. I would like to completely disable this. There are
> > queries which pull specific information for each user from these 5
> > tables and this is the only way that I would like users to view
> > information. I do not want them opening the original tables at all. Is
> > this possible? I would appreciate your help.
>
> > Thanks,
> > Sam- Hide quoted text -
>
> - Show quoted text -
Thank you for the response. I have built the front-end so that users
can only view/edit the information that pertains to them- no MS Access
knowledge needed. However, there are about 50 users of the database I
am building- so I can't be too sure whether someone would know how to
unhide tables and open them. How can I prevent this- besides hiding
the tables? Is there anyway to code in VBA to disable opening of
tables and only allow the database to open the forms? I've also
already disabled the navigation pane and enabled a startup splash
screen. However, advanced users would be able to hold SHIFT down when
opening the file to gain access to the navigation pane. Any other
suggestions?
|
Similar Threads
