I need to build a database or databases!!!

The question I present here, should I build one database or break it down into several databases.

The Uses:

We provide a service that includes labor and material. But first we estimate what will be needed. Then a sales person attempts to sell it. If we sell it a group of people go out and perform the service.

So the database(s) needs to track the requests for the estimates, be used to build the estimates, be used by the salespeople to build presentation to help them sell the service. And finally be use to track the progress of the service.

I was all set to build 2, 3 or even more databases but it hit me that at least one table would be repeated in each case, employees.

The only other consideration is the need to limit access to certain parts. For example a Salesperson can not change the estimate details.

There are more common tables than just employees. I would either build a single application and use Access to control access to particular objects or build a single back end with all the tables and multiple front ends, one for each application area.

If there is not a lot of overlap in the functionality, the several fe's against a single be may prove to be the most flexible solution.

Thats what I thought, but was not 100% sure. Thank you for the reply.