Web Development

Read up on setting up security within Access. It's pretty ugly, but you can control the access to every table, query, form and report for every user or group of users. Sounds to me like you have three user groups: those that can only view, those that can enter data, and the owner/admninistrator (yourself). The downside is that the security may not be separate from the customized database, which will mean that you may need to re-do all these security-related changes any time there's an upgrade from the vendor. I'd talk to the database vendor before making any changes.

Depending on the version of Access that was used to develop the database, and the method chosen by the developer, the database will use Jet (the native Access database engine) or some version of SQL Server.

If SQL Server then you have more capability for granting or denying access to the database.

Either way, you are at the cusp of the capability for concurrent users of an Access application (depending on how it was written). Access, by default, does it's own record locking, etc. which degrades as more users are added. Connecting with SQL Server helps extend that number of concurrent depending on what method the data is presented to the user.

Ultimately, if your application does not already have roles defined in it providing security, you are going to have to modify the application to restirct access, or write a different applicaiton for your non-employee users in order to assure they don't have access to restricted data.

Cheers,

Ben

This question was closed by the author