I've read all the previous posts hoping someone would have a very simple answer. I have created a form that will have data entered into it by 1 maybe 2 users (I use similar forms all the time). However, I have 3 more users that will need to have viewing but not editing capabilities. The data base will be stored on a shared-drive within our system. Splitting the db seems very complicated and still does not prohibit my users from entering or modifying existing data in the form/table. And I'm not certain if I fully understand the "read-only" option (which is what I want) where I have to rename the db. Is there a simple answer out there? I can do this in Word forms and can even block access to cells in Excel...just can't figure out how to do it in Access. Please help! :banghead:
Multi-VIEWERS, not users
- Thread starter Tonia
- Start date
Rx_
Nothing In Moderation
- Local time
- Today, 08:29
- Joined
- Oct 22, 2009
- Messages
- 2,803
Welcome with your 2nd post.
Read-only can be accomplished in more than one way.
It is possible to set one single DB so that one or more individual user is read-only.
Can you give us a little more information?
What is your programming skill level?
Splitting your DB is actually fairly easy. Going forward, there might actually be much less maintenance on a split DB. The data is on the Back-End. The Users (on the FE or Front-End) can be limited to Read Only. It is also possible to put a simple password on the Back End DB to prevent casual unauthorized entry.
Basically, on your Start Form, the user ID can be determened. In my case, I have a table of users in the back-end that determine what forms are read-only and what forms are read-write for each user.
Read-only can be accomplished in more than one way.
It is possible to set one single DB so that one or more individual user is read-only.
Can you give us a little more information?
What is your programming skill level?
Splitting your DB is actually fairly easy. Going forward, there might actually be much less maintenance on a split DB. The data is on the Back-End. The Users (on the FE or Front-End) can be limited to Read Only. It is also possible to put a simple password on the Back End DB to prevent casual unauthorized entry.
Basically, on your Start Form, the user ID can be determened. In my case, I have a table of users in the back-end that determine what forms are read-only and what forms are read-write for each user.
Programming skill level - intermediate, but always willing to learn more. However, I just found out that 2 of my 3 additional users have not been upgraded to ACC2010 so will be unable to view the db anyways at this time. I am going to try splitting it in case our IT Tech upgrades everyone soon. I will then try the password/read-only for the FE users. Thanks for the (clearer) suggestion. -T
GinaWhipp
AWF VIP
- Local time
- Today, 10:29
- Joined
- Jun 21, 2011
- Messages
- 5,899
