=?Utf-8?B?TWlrZSBEaWFtb25k?= <MikeDiamond@discussions.microsoft.com>
wrote in news:3BF77103-AE74-4ACB-9C0F-15B97590EBE5@microsoft.com:
> As an example; We want to go for a project for Microsoft to build new
> HQs. We put together a submission offering our services and propose a
> consortium, consisting of 2 internal team members, a Project Managment
> Company, a Quantity Surveying Firm and a Construction Company.
From such a very brief description, I'd suggest you probably need tables
like this:
Commissioners (commissionerID, fullName, address, creditStatus, etc)
Submissions (dateMade, currentStatus, owner, etc)
SubmittedTo (submissionID, commissionerID)
TeamMembers(memberNum, submissionID, roleInTeam, etc)
Members(memberNum, commissionerID)
Companies(memberNum, normalTitle, nameOfContact, address, etc)
People(memberNum, fullName, isAnEmployee, etc)
but it might be a bit more complex than that once you have started
analysing it properly.
Hope it helps
Tim F
Hi Mike,
What is the issue? There are many ways to get members of two
different sets to show up in a single output document. It may be that
you're trying to associate which candidates are related to which
submission??
One way to solve that would be to create a table
~tblSubmissionsCandidates which is on the many side of a one-to-many
relationship with tblSubmissions.
HTH

Signature
-Larry-
--
> Hi All
>
[quoted text clipped - 29 lines]
> Regards
> Mike