FE/BE DB's and security issues

[sterlecki]

I am about to undertake my first Application DB that will be split and have security with it. Previous efforts have been stand alone apps.

1. Should security be added before or after splitting the app?

2. I plan to create copies of the front end to place on users local machines. Once security has been added to the FE will it also become part of the copies that I create from the secured version or will I have to add it to each copy?

3. I would like to protect the current queries, forms and code from the users but allow them to create their own tables, queries, forms, macros etc. Will the security measures for groups allow this?

4. Any other cautions or gotchas that I should be aware of before attempting this?

Thanks for your help.

 

[RoyVidar]

What db?

The question might be better addressed in a forum dedicated to the technology you're using. There's a "smell of Accesss" over this, I'd suggest search the seven dedicated Access fora, perhaps in perticular Access Other topics (forum181)...

Roy-Vidar

 

[sterlecki]

Yes this is an Access project. I thought I had posted this in the appropriate area as I saw similar posts regarding FE/BE dbs.

Sorry

 

[ceh4702]

There are a few issues here. Security comes in layers. The database layer, the application layer and the client layer. Between the application and the database there may need to be an SQL server layer. Sometimes all the layers are on one server or the application, the SQL, and the database are all on separate boxes. This all involves system architecture more than database design, but it has to be considered. Splitting up the the database and the application with an sql server in the middle makes it faster and more compartmentalized. It is possible to separate the database from the application to make them completely independent.

If you do not like my post feel free to point out your opinion or my errors.