View Only for a Multiuser
CDG via AccessMonster.com
users will only be using the database as a view only and will not be allowed
to edit/enter information. Is there a way to do this?
Thanks,
CDG
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200911/1
Armen Stein
<u17949@uwe> wrote:
>There will be multiusers entering information into a database. One of the
>users will only be using the database as a view only and will not be allowed
>to edit/enter information. Is there a way to do this?
There are a few ways to do this:
Hopefully you've already split your system into a front-end
application and back-end database. If not, do that first!
- If you are using MDB format, you can use Access User Level Security
to make two different permission groups in a workgroup file - one that
allows updates, and one for read-only. This isn't trivial, however.
You need to learn about configuring ULS in your database. Here's a
place to start:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html#Security
- If your application is simple, you can give the read-only user a
different version of the front-end where the controls on the forms are
Locked.
- Or you can give the RO user a copy of the back-end database each
day, and tell them not to bother making any changes because they will
be overwritten periodically.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com
CDG via AccessMonster.com
Thanks for the info on security - a little more than I can do. I do like the
idea of using 2 different versions. I am guessing that you mean to create
two forms - 1 for editing and 1 for viewing or do you mean create 2 different
databases.
Thanks,
CDG
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200912/1
Armen Stein
<u17949@uwe> wrote:
Hi CDG,
>My database is not split. What is the purpose of a front end and back end?
Splitting your Access database is considered a *must* with experienced
developers. Bing or Google Access Split Database for many articles,
including avoiding corruption, increasing performance and managing
application changes. http://allenbrowne.com/ser-01.html is a good
place to start.
You'll need a way to maintain your linked tables. You're welcome to
use our free J Street Access Relinker at:
http://www.jstreettech.com/downloads
It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There's a ReadMe table with
instructions.
>Thanks for the info on security - a little more than I can do. I do like the
>idea of using 2 different versions. I am guessing that you mean to create
>two forms - 1 for editing and 1 for viewing or do you mean create 2 different
>databases.
I actually meant a separate Access front-end MDB with read-only forms
in it. That way your RO user (hopefully a novice who won't go poking
around) won't have the updatable forms to tempt them.
Cheers,
CDG via AccessMonster.com
as well as a lot of work to do - back to the drawing board.
Have a great day,
CDG
--
Armen Stein
<u17949@uwe> wrote:
>Thank you Armen for all that information. Wow, I have a lot to think about,
>as well as a lot of work to do - back to the drawing board.
You're welcome - drawing boards are my specialty. :)
But the good thing about drawing boards is that a simple eraser can
correct any mistakes.
mariamaria
Armen Stein wrote:
There are a few ways to do this:Hopefully you have already split your system
11-Dec-09
There are a few ways to do this:
Hopefully you have already split your system into a front-end
application and back-end database. If not, do that first!
- If you are using MDB format, you can use Access User Level Security
to make two different permission groups in a workgroup file - one that
allows updates, and one for read-only. This is not trivial, however.
You need to learn about configuring ULS in your database. Here is a
- If your application is simple, you can give the read-only user a
different version of the front-end where the controls on the forms are
Locked.
- Or you can give the RO user a copy of the back-end database each
day, and tell them not to bother making any changes because they will
be overwritten periodically.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com
Previous Posts In This Thread:
On Friday, December 11, 2009 1:42 PM
CDG via AccessMonster.com wrote:
View Only for a Multiuser
There will be multiusers entering information into a database. One of the
users will only be using the database as a view only and will not be allowed
to edit/enter information. Is there a way to do this?
Thanks,
CDG
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200911/1
On Friday, December 11, 2009 3:37 PM
Armen Stein wrote:
There are a few ways to do this:Hopefully you have already split your system
There are a few ways to do this:
Hopefully you have already split your system into a front-end
application and back-end database. If not, do that first!
- If you are using MDB format, you can use Access User Level Security
to make two different permission groups in a workgroup file - one that
allows updates, and one for read-only. This is not trivial, however.
You need to learn about configuring ULS in your database. Here is a
- If your application is simple, you can give the read-only user a
different version of the front-end where the controls on the forms are
Locked.
- Or you can give the RO user a copy of the back-end database each
day, and tell them not to bother making any changes because they will
be overwritten periodically.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com
On Friday, December 11, 2009 8:54 PM
CDG via AccessMonster.com wrote:
My database is not split. What is the purpose of a front end and back end?
My database is not split. What is the purpose of a front end and back end?
Thanks for the info on security - a little more than I can do. I do like the
idea of using 2 different versions. I am guessing that you mean to create
two forms - 1 for editing and 1 for viewing or do you mean create 2 different
databases.
Thanks,
CDG
Armen Stein wrote:
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200912/1
On Saturday, December 12, 2009 12:24 PM
Armen Stein wrote:
Hi CDG,Splitting your Access database is considered a *must* with
Hi CDG,
Splitting your Access database is considered a *must* with experienced
developers. Bing or Google Access Split Database for many articles,
including avoiding corruption, increasing performance and managing
application changes. http://allenbrowne.com/ser-01.html is a good
place to start.
You'll need a way to maintain your linked tables. You're welcome to
use our free J Street Access Relinker at:
http://www.jstreettech.com/downloads
It handles multiple Access back-end databases, ignores ODBC linked
tables, and can automatically and silently relink to back-end
databases in the same folder as the application (handy for work
databases or single-user scenarios). There is a ReadMe table with
instructions.
I actually meant a separate Access front-end MDB with read-only forms
in it. That way your RO user (hopefully a novice who will not go poking
around) will not have the updatable forms to tempt them.
Cheers,
Armen Stein
Microsoft Access MVP
www.JStreetTech.com
On Saturday, December 12, 2009 5:16 PM
CDG via AccessMonster.com wrote:
Thank you Armen for all that information.
Thank you Armen for all that information. Wow, I have a lot to think about,
as well as a lot of work to do - back to the drawing board.
Have a great day,
CDG
Armen Stein wrote:
On Sunday, December 13, 2009 2:19 PM
Armen Stein wrote:
You're welcome - drawing boards are my specialty.
You're welcome - drawing boards are my specialty. :)
But the good thing about drawing boards is that a simple eraser can
correct any mistakes.
Armen Stein
Microsoft Access MVP
www.JStreetTech.com
Submitted via EggHeadCafe - Software Developer Portal of Choice
BOOK REVIEW: Effective C#, Second Edition [Addison Wesley]
http://www.eggheadcafe.com/tutorials/aspnet/b2f8766d-a4c1-4d5a-97af-c38852b3b455/book-review-effective-c.aspx