By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,099 Members | 947 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,099 IT Pros & Developers. It's quick & easy.

primary key problem...

P: n/a
Hi there, i have a problem defining my primary key...

I have a list of material (tools) that i manage. I want to be able to
track them (follow information that people enter) in the database. I
set my primary key to ID_Material but my question is?

If i send my tools twice to get fixe should i use this key or another
1 like.
Cuz if i use the id_material ans i want to send the tool twice it will
be double in my DB but with a different date.
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
You need two tables, one to identify tools and one to track repairs to the
tools. Like:
TblTool
ToolID
<other fields about a tool>

TblToolRepair
ToolRepairID
ToolID
RepairDate
<Other fields about a repair>

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
"yugo" <ug********@hotmail.com> wrote in message
news:fc**************************@posting.google.c om...
Hi there, i have a problem defining my primary key...

I have a list of material (tools) that i manage. I want to be able to
track them (follow information that people enter) in the database. I
set my primary key to ID_Material but my question is?

If i send my tools twice to get fixe should i use this key or another
1 like.
Cuz if i use the id_material ans i want to send the tool twice it will
be double in my DB but with a different date.

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.