Securing a Split Mutli-User Database

[TastyWheat]

I don't have the database finished so I can't really comment on the structure. However, I know the database will be used by multiple people, very likely at the same time. I've heard it's a good idea to split the mdb into a frontend and a backend so I've already started that process. I have no idea how this would fit into a security scheme though. Do I have to set up user-level security on both ends? Without actually implementing it I kind of think it would be secure if the backend had a master password and the frontend had user-level access. What do you all think?

 

[RCurtin]

The easiest way to do it is to secure it first using user level security and then split it. That way when you split it both the backend and front end will have the same security and you only have to do it once.

Splitting it is quite easy. You just have your tables in one database (the backend) and everything ( queries, forms etc in the other) else in the front end. Then you link to the tables in the backend from the frontend and link to the tables in the backend.

From what I've read setting a database password is not much use as it can be hacked quite easily.