Custom front end files and restrictions?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mike M - 12 Sep 2003 00:09 GMT

We have several departments that use the same database but not all need
access to the same form, data, or field.
We only just split the DB today after years of using it in a whole
single DB form, and I am not sure of all I can do with it yet.
Can I delete a form or table on an FE without causing the same
information to be deleted at the server? Or should/can the FE be made
limited in the first place?
Also can we restrict users from modifying or customizing the local FE so
as not to query or report info they don't need?
Whoops just got the answer about deleting the links. Access told us it
is only the link but not the data.

Signature

Mike Moore
Computer Services Technician
Snow Summit Mt. Resort
Office (909) 866-5766 Ext.270
mikemoore@ www.snowsummit.com
Contact info not for share, rent or distribution.

Reply to this Message

Larry Linson - 12 Sep 2003 03:36 GMT

> . . .
> Also can we restrict users from modifying
> or customizing the local FE so as not to
> query or report info they don't need?

Visit http://www.microsoft.com/downloads and get a copy of the Access
Security FAQ. Read, study carefully, and then ask questions. Using a
developed Access application with properly implemented security can prevent
the users from modifying their front end databases or retrieving data they
aren't supposed to have.

But, be warned, it's not a trivial task. There's even a separate
microsoft.public.access.security newsgroup. The FAQ prints out as 39 pages
and none of the information there is "filler".

Please follow up or clarify here in the newsgroup, not by e-mail. Thanks.

Larry Linson
Microsoft Access MVP

Reply to this Message

Mike M - 16 Sep 2003 21:53 GMT

Well after searching several different ways I still do not see the FAQ
you suggested.
If you have a page link it would be appreciated.

| > . . .
| > Also can we restrict users from modifying
[quoted text clipped - 15 lines]
| Larry Linson
| Microsoft Access MVP

Reply to this Message

Mike M - 16 Sep 2003 21:56 GMT

Never mind I found it.

Reply to this Message

HSalim - 18 Sep 2003 05:34 GMT

> We have several departments that use the same database but not all need
> access to the same form, data, or field.
> We only just split the DB today after years of using it in a whole
> single DB form, and I am not sure of all I can do with it yet.
> Can I delete a form or table on an FE without causing the same
> information to be deleted at the server?

Yes, as you just found out.

Or should/can the FE be made

> limited in the first place?
> Also can we restrict users from modifying or customizing the local FE so
> as not to query or report info they don't need?

If you compile your access db into an MDE, a compiled application, then
users will not be able to build new queries
or even open linked tables if you design your tables correctly.
You must also implement security to prevent them from creating a new access
database and simply linking to your BE, bypassing your FE
altogether. There are many options relating to security, and you can make
it fairly secure - preventing access to all but the most knowledgeable and
determined

HS

Reply to this Message

Mike M - 18 Sep 2003 20:54 GMT

| > We have several departments that use the same database but not all need
| > access to the same form, data, or field.
[quoted text clipped - 19 lines]
|
| HS

Thanks, I was looking into the MDE solution already.
Mike

Reply to this Message

Rick Brandt - 19 Sep 2003 01:30 GMT

> > We have several departments that use the same database but not all need
> > access to the same form, data, or field.
[quoted text clipped - 12 lines]
> users will not be able to build new queries
> or even open linked tables if you design your tables correctly.

An MDE does NOT impose any restrictions on queries or tables. Only code based
objects. You can still make new Tables/Queries and edit existing ones.

Reply to this Message