I am in the process of building a stand-alone version of our company's quotation package for distribution to our sales force.
The system currently reads the required data from an internal Oracle database but I am changing it to read from an Access database. The issue I want to solve is that the data is extremely confidential and needs to be
protected from unauthorised access, in this case it should only be readable by the actual quotation application.
I believe it should be possible to do this with Workgroup security but having never used this in the past I am looking for some pointers on how exactly to go about this.
Some rough ideas I've gleaned from various books and sites
1) Create a new workgroup file for the database
2) Create a new user and add to Admins group
3) Remove Admin user from Admins group
4) Import tables and queries into a new database using new user so new user takes owenership
5) Clear the rights from the Admin user and the Users group to limit their access as required.
6) Add a database password, not sure if this is required at all for my purposes
7) Add a new group with read only rights as required for the application and create a user in this group for use by the application through ADO connections to the database
8) Provide the workgroup file with the database in the application install so read only user available to the application
My issue is what rights do I need to remove from the Admin user and the Users group in order to ensure that they will not be able to see any of the data, I don't care if they can open the database so long as they cannot view any of the data or link to it or import it into another database.
Also is there anything else that needs/should to be done in order to limit the access to the data.
The system currently reads the required data from an internal Oracle database but I am changing it to read from an Access database. The issue I want to solve is that the data is extremely confidential and needs to be
protected from unauthorised access, in this case it should only be readable by the actual quotation application.
I believe it should be possible to do this with Workgroup security but having never used this in the past I am looking for some pointers on how exactly to go about this.
Some rough ideas I've gleaned from various books and sites
1) Create a new workgroup file for the database
2) Create a new user and add to Admins group
3) Remove Admin user from Admins group
4) Import tables and queries into a new database using new user so new user takes owenership
5) Clear the rights from the Admin user and the Users group to limit their access as required.
6) Add a database password, not sure if this is required at all for my purposes
7) Add a new group with read only rights as required for the application and create a user in this group for use by the application through ADO connections to the database
8) Provide the workgroup file with the database in the application install so read only user available to the application
My issue is what rights do I need to remove from the Admin user and the Users group in order to ensure that they will not be able to see any of the data, I don't care if they can open the database so long as they cannot view any of the data or link to it or import it into another database.
Also is there anything else that needs/should to be done in order to limit the access to the data.
