I have a patient database shared among 10 people. Is there any way to prevent
these users from going into the design view of the tables? I don't want
anyone messing with the table structure.
Yes there is. But, how are they viewing the information? Have you tried any
startup options? ETC.
> I have a patient database shared among 10 people. Is there any way to prevent
> these users from going into the design view of the tables? I don't want
> anyone messing with the table structure.
Andi - 02 Jul 2005 16:19 GMT
I can't hide the tables on startup as sometimes the users have to access the
information in the tables directly. I tried splitting the database so the
tables would be the backend linked to the forms and stuff for users. However,
the application worked extremely slow and the users complained.
I did not design the database myself. I inherited it when someone left and
there is no documentation anywhere as to why he did what he did.
> Yes there is. But, how are they viewing the information? Have you tried any
> startup options? ETC.
>
> > I have a patient database shared among 10 people. Is there any way to prevent
> > these users from going into the design view of the tables? I don't want
> > anyone messing with the table structure.
Split your database -- the back-end will hold tables and the front-end will
hold everything else.
Give your users the front-end. They could still, with perserverence, see
the tables, but they won't be able to modify them.
Check Access HELP on "splitting" your database.
Good luck
Jeff Boyce
<Access MVP>
>I have a patient database shared among 10 people. Is there any way to
>prevent
> these users from going into the design view of the tables? I don't want
> anyone messing with the table structure.
Andi - 02 Jul 2005 16:20 GMT
I did try splitting the database but the linked front end worked extremely
slow and the users complained.
> Split your database -- the back-end will hold tables and the front-end will
> hold everything else.
[quoted text clipped - 12 lines]
> > these users from going into the design view of the tables? I don't want
> > anyone messing with the table structure.
Jeff Boyce - 02 Jul 2005 17:22 GMT
There are many reasons why a split design can be slow. If you want to
investigate this further, check Tony's website:
http://www.granite.ab.ca/accsmstr.htm

Signature
Good luck
Jeff Boyce
<Access MVP>
> I did try splitting the database but the linked front end worked extremely
> slow and the users complained.
[quoted text clipped - 15 lines]
> > > these users from going into the design view of the tables? I don't want
> > > anyone messing with the table structure.