monkeytunes
Serf of the Jungle
- Local time
- Today, 09:30
- Joined
- Jun 8, 2004
- Messages
- 120
Hey there buddays...
I have a rather large database that is split into a frontend and a backend.
The backend resides on a shared drive while the frontend is on individual users (about 5 or 6) desktops. I can't do any administration on the shared drive, i.e. I can't hide the backend from users, nor can I change any read-write permissions.
The powers-that-be have decided that security should be implemented. I've implemented Access Security before, as well as some of the password management schemes presented on these boards, but what I've never done is try to secure a database that is split, used by multiple people and where the backend is on a server.
If anybody knows of/has some step-by-step instructions as to how to secure a database with these parameters (1. split, 2. multiple users with frontends on their own machines, 3. backend on a shared drive which is administered by the monolithic and unforgiving IT department), I'd be muchos appreciative.
I have a rather large database that is split into a frontend and a backend.
The backend resides on a shared drive while the frontend is on individual users (about 5 or 6) desktops. I can't do any administration on the shared drive, i.e. I can't hide the backend from users, nor can I change any read-write permissions.
The powers-that-be have decided that security should be implemented. I've implemented Access Security before, as well as some of the password management schemes presented on these boards, but what I've never done is try to secure a database that is split, used by multiple people and where the backend is on a server.
If anybody knows of/has some step-by-step instructions as to how to secure a database with these parameters (1. split, 2. multiple users with frontends on their own machines, 3. backend on a shared drive which is administered by the monolithic and unforgiving IT department), I'd be muchos appreciative.