Re: help: design issues

#1

Make a junction table that will contain 3 columns: projID, namesID and jobDate.
Populate the table with combinations of assigned IDs. Relate the primary
keys to projects and names, and run queries to retrieve the assignment information.

Good luck,
Pavel

spamspamspam wrote:

Quote:

projects table:

projID project
-----------------
64533 DoSomething
74236 DoAnotherThing
-543645 LastThing

names table:

namesID first last
------------------------------
-643234 billy bob
08745 sue NO_LAST
-23454 NO_FIRST smith
567833 NO_FIRST NO_LAST

(side issue, there shouldn't be two billy bob's, ignoring BILLY BOB v
billy bob)

billy bob, sue, and mr/mrs smith are all working on DoSomething.
Sue's also working on DoAnotherThing. LastThing doesn't have anyone
"assigned" to it yet, so NO_FIRST NO_LAST is doing that project, the
default entry.

as new projects are entered with the AddProjects form, there needs to
be some mechanism to enter billy bob, sue, and smith, and to connect
them to a particular project.

is the answer a bound combo box, with cascade update/delete,
referential integrity, many names to one project, blah blah blah.

ok, how do i do this, please?

"spamspamspam"
mapsmapsmaps (AT) mail (DOT) com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: help: design issues

comp.databases.ms-access comp.databases.ms-access

Re: help: design issues - 08-05-2003 , 02:02 PM