Steve said:
<<If I understand correctly there can only be two designers working on the
database at any one time; one in the front-end and one in the back-end. >>
That is incorrect! Any number of designers can work on developing the
tables in the backend. Each designer can be working in a separate file
creating his set of tables. There needs to be a master backend file where
when a designer is completed with his part, his tables are imported into
the master. When all the designers are completed and all their tables are
in the master, the relationships can be created between all the tables in
the backend.
Once the backend is completed, then any number of designers can work on
the frontend. Again there needs to be a master frontend where each
designer's work can be imported into when the the designer is complete
with his part.
But really it takes about 3 minutes to input a table. The overall design is
what is important, and it makes no sense to have more than one person
independently designing the table structure. If a team _does_ design the
tables, it's more effective to have them all around a table discussing the
overall design and hashing out the best relational structure. After that,
implementing the design is a few hours' work for one person at most.
I do agree with Steve that you can have multiple files and import all the
components into one master file, but it seems to me to make more sense to do
that with the _frontend_, where having multiple people working on forms and
code makes more sense.
-Amy