Question Limiting view

[SueBK]

I have a database with about 80 projects in it. Huge thing with twenty-eleven different aspects of each project being reported. The prime purpose of the database, other than to collate information, is to enable project managers to produce a monthly report easily.

I have two anomolies. One I think is easy to overcome, one ... not so easy.

First - one project manager produces a single monthly report that covers about 30 projects. Some aspects of the report are an overview of the entire 30 projects, some are selected items of each project. For example: he reports total financial figures for the projects as a group (ie treats them as a single major project), but he reports risk issues against each individual project.

I figure - set up a 'bogus' project called "compiled projects" (or some such thing) that uses queries to compile the compliled data and allows him to enter the other information as a single report. Painfully amount of re-work for us, but easy in theory.

The second is very similar. The entire project group is reported in a single report, very similar to the first issue. BUT (BUT) this report is confidential. Normal level project managers aren't supposed to have access to it. Now, I could treat it the same way as the compiled projects - but how do I limit viewing? I've never set security on a database before (other than simple "you-can't-design" security).

Will I have to create a separate table for this one "project"? Or can I create another "compiled project" and limit access to the single record?

 

[neileg]

Duplicating data in different tables is almost never the right answer. Depending how secure your security needs to be, you could split that database and use different front ends to give diferent levels of access. There are other approaches, too. Depends what you want.

 

[SueBK]

The end decision was - to create separate tables/form/reports for the overall report (ie the report that reports on ALL projects). There's some fundamental differences in the information reported on; compared with the reporting of individual projects. This gets over the security issue. The command button that allows access to the overall report is password protected.

The other issue - the compiled projects report is next on my list. The report is exactly the same as the individual project report, just reports them as a group; so we will create a 'dummy' project.