Users and passwords

[Anita]

I am using version 2003.

I want to distribute my database to a number of people and give them log on
usernames and permissions but don't know the best way to go about it.

Should I split my database first of all so that the tables are separate from
the other objects, but then having done that can I then give users
permissions aswell. I'm not really sure what I should be doing so any help
gratefully received.

I've fiddled about with the database splitter before and have read about
encrypting and setting permissions but do you do all of those things or not?

Please help - I know quite a bit about Access but not a lot in this area -
so not totally novice, but need a bit of advice.

Many thanks

Anita

 

[S Panja]

The database has to be split at one time or other prior to distribution.
Subsequently necessary permissions are to be assigned - on the database and
the network.
--
***************************
If the message was helpful to you, click Yes next to Was this post helpful
to you?
If the post answers your question, click Yes next to Did this post answer
the question?

 

[jacksonmacd]

Splitting and permissions are independent. You should always split
your application, then apply permissions to the backend portion as
required. You typically distribute the frontend as an MDE.

I prefer to handle these steps manually, foregoing the wizards.
Splitting manually is easy -- just make two new copies of your
database. Delete all the tables from one (the frontend) and delete all
the other stuff from the other (the backend). Use File > Get External
Data > Link to link from the frontend to the backend. See Tony Toews'
site for lots of good information:
http://www.granite.ab.ca/access/splitapp/index.htm
You will also want to look into Tony's method of distributing updates
to your frontend;
http://www.granite.ab.ca/access/autofe.htm


As for security, there are lots of good resources to help you through
it. See the website in my signature for my own process plus links to
others.

I am using version 2003.

I want to distribute my database to a number of people and give them log on
usernames and permissions but don't know the best way to go about it.

Should I split my database first of all so that the tables are separate from
the other objects, but then having done that can I then give users
permissions aswell. I'm not really sure what I should be doing so any help
gratefully received.

I've fiddled about with the database splitter before and have read about
encrypting and setting permissions but do you do all of those things or not?

Please help - I know quite a bit about Access but not a lot in this area -
so not totally novice, but need a bit of advice.

Many thanks

Anita

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security

 

[Anita]

Thats great Thanks

Splitting and permissions are independent. You should always split
your application, then apply permissions to the backend portion as
required. You typically distribute the frontend as an MDE.

I prefer to handle these steps manually, foregoing the wizards.
Splitting manually is easy -- just make two new copies of your
database. Delete all the tables from one (the frontend) and delete all
the other stuff from the other (the backend). Use File > Get External
Data > Link to link from the frontend to the backend. See Tony Toews'
site for lots of good information:
http://www.granite.ab.ca/access/splitapp/index.htm
You will also want to look into Tony's method of distributing updates
to your frontend;
http://www.granite.ab.ca/access/autofe.htm


As for security, there are lots of good resources to help you through
it. See the website in my signature for my own process plus links to
others.






**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security