Thank You. Very helpful tip.
Main Topics
Browse All TopicsI have a joined database consisting of Individual data, Membership data and donation data. I want to keep the donation data restricted to 2 people, but I can allow all the staff (7-8 others) to view membership data. The thought I have is to build two APR files and not link in the donation data on one of them. My question is this - If people are accessing the data simultaneously from different APRs, am I exposed to data loss? Is this a reasonable approach?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: VolleyTomPosted on 2005-03-28 at 11:25:29ID: 13646174
Look at Team Security. It should let you to do what you want without creating separate APRs. You can hide views from lower level users, make certain data read only, limit their ability to create new views, etc.
You can use multiple APRs to access/view the underlying DBFs but it's generally not as efficient -- especially for maintainance. You at least need to consider what you're doing carefully to make sure linked fields are updated properly. For example, you may want someone to be able to add a new donation but not see donation history. I think this would be easier with Team Security. Others may have different ideas.