Access and security usually leads to some sort of concession.
Is the backend located on the network? Can you have people with write permission to the database log in with a special workgroup (join it through access or use a shortcut)? Is it o.k. for readers to be able to delete the database?
Do readers and writers need simulatneous access to the file?
Hi
The database is located on network and it should be read-only for users. User wants to create their own report (using crystal) report that is why the should not have any other access except read-only.
it's not particularly brilliant, but it will allow you to set up users, groups, and then set specific permissions like read/write/modify design... against tables/forms/reports for those users or groups.
But if you are the only one making changes I would not publish the workgroup. Instead I would give the admin user (which is common to all workgroups) read permissions only.
Then only you have to worry about the workgroup. This is particularly useful if it is being read by a program that does not support workgroups (I don't know about Crystal).
To create a workgroup go to Tools, security and workgroup administrator and hit create. You will later want to either join it or use a command line switch to open access with it. This is just a nudge in the right direction like Crowley16 said.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.