database config help

[glennn1137]

i have to make two tables in a db that link to each other and i'm an idiot - here goes. client buys a membership for a year to put a registered bumpersticker on their teen's car that says "If you see my teen driving like a madman/woman call this 800 number or visit this website and report it"...

k? one table holds member info, 2nd table captures incident reports as they are called in / input with an association to the members id # that will be on the bumpersticker of said maniac teen's automobile...

the common item is obviously the decal number assigned to member, and the reporting narc uses it when reporting if possible...

i don't know exactly how i want to tie these two tables together so that an incident report will correspond with the member who owns the decal # . make sense? can someone help?

thanks ever so much,
glenn

[ultraslacker]

Google for relational database design.

Briefly, here's how I would sketch the database. I'm assuming that a client can have many reports, but only one decal number.

[clients]
id (decal #)
name
...

[reports]
id
client_id
...

[glennn1137]

outstanding, thanks for your help -

q. - there is no need to have an auto incrementing number is there, since the decals are preprinted and will be assigned to a client arbitrarily? the common id's could simply be input along with the member's other info...? then referred to when a report is made...?

thanks much,

glenn nall

[barand]

I would make the decal # the primary key to ensure no duplicates (preprinting isn't an absolute guarantee)

Have the report id an auto_incrementing primary key. Put an index on report.clientid (allowing duplicates)