Splitting a Table for Security

[TastyWheat]

I'm on a project to build a database for the stores in our area. Things like managers, banks, and partners obviously should be in seperate tables. Most of the information though, seems to belong directly in a table of stores. Basically each record is a store and there will be very many attributes per record (about 30+). Some attributes only relate to certain departments and only someone from that department should see that info. If I broke up the big table into smaller tables it would be the same information but every table would have to have the store number to link it all back together. From a design standpoint this is bad because the store number is redundant.

So my question is, is it a good idea to split up the table for security purposes?

My main concern is security, I can take a hit on performance or storage.

 

[ghudson]

Use Access security with a custom workgroup and user permissions. Filter the data base on the user or division or store. Splitting a table for security reasons does not make sense. The users should never see the tables if the database is correctly secured. The users should only have access to the forms and you program their navigations and what they can see [access]. Search the forum for more information on how to secure your database.