I am thinking of setting up a database that can be used by our enterprise. A single Database that contains information (demographic data) about our employees to be used by our Human Resources Department, Training information to be developed by our Staff Development Department. A fiscal resources page to be used by our Financial Department and page for disability and insurance related claims administered by our
Workman's Comp Department.

All of this information collected represents the sum total of every employee.  However, each department does NOT need to see the other's data and information. We are talking compatmentalizing the information yet giving access to those that truly need access to the whole picture. This of course resides on a server giving shares to  the whole application as projected by security, hiding pages (databases) that aren't relevant.

I have no trouble setting up the databases themselves, yet I haven't quite figured out how to make the different pages visible to the right people.

I have considered using the capabilities of Novell to set up the security access by allowing User ID's access to relevant parts or "groups". This is problematic in that I can't link the various groups without giivng access to all.

What I would like to do is to build a tab based database and program in Sbasic access to each of the tabs for each separate group. How would I go about it if it can be done at all? GJK..

I guess, as a start, I would recommend that you use three different applications, each with group based security, and each running on a different Sesame server using unique port addresses. Then set up the port numbers on the appropriate clients so that they access only the appropriate Sesame server. If the port numbers "leak" to an inappropriate dept. you will still have group password in place to fend off unwanted access. Folks that should have access to all the applications, get icons for each (with appropriate port numbers in the "Target") and are included in the group security on all the apps.

Bobscott, I could see your idea working if access to all of the other subforms was blanked out except for the one that you would have immediate rights.  Somehow you would have to tie this into your immediate rights. So as you opened the related database subform, that would be the only thing that you could see. Interesting...

Don't forget about security if users will be able to generate reports.  Would want to have group security at the field level to prevent unauthorized access of data from reports. 

Also same issue with Export, and File copy. 

What about keeping data in separate folders with network access security?  With some XLU programming for common shared data?