1) tblSkateboard
Skateboard ID (this is nothing but product ID to identify skateboard product)
Skateboard Model ( is a description of the skateboard)
Description ( a detailing about the skateboard )
OtherDetails (more information about the skateboard)
The table has specific information about skateboard. The product we will be selling tomorrow.
2) tblsupplier
SupplieID (ID for supplier)
Supplier Name ( Name of Suppliers )
SupplierContact (address of suppliers for correspondence)
Address
City State
Phone
Fax
Email
Active (this checks if we want to continue to buy from this supplier)
3) tblProducts
ProductID
Description
Quantity
Price
Image
4) tblCustomers
Customer Name
City
State
Zip
Active (this verifies if the users is active or not, as we disable the customer for not following the rules).
5) tblOrders
OrderID
OrderDateTime (order placed date and time)
ProductCount (number of product)
Item Total (total count)
Grand Total
ShipmentDate (when the item is being shipped)
PaymentMethod (Visa, paypal, or Money Order)
ShipmentComments (this indicate if this order is processed out or not)
SpecialComments (any special notes; from sales or assistance)
6) tblAccessories
AccesoryID
Acessoryname
ProductID (to which product this accessory associated)
SupplierID ( supplier ID of the accessory supplier)
Weight (LBS, capacity)
Condition ( refurbished, new, or used)
Otherdetails (other special notes)
Image (image of accessory)
7) tblEventCodes
eventCode
Event Description (promotion 10% off)
Event Other Details ( special note about the promotion)
This table has codes for each event. Example, Skateboard competition has code (sc), this is a completion for promoting sale of skateboard which will be conducted in New York.
8) tblBearingTypes
bearingID
BearingType (ball bearings double ball bearing)
9) tblWheelType
WheelID
WheelType (small, medium, large, xxlarge)
10) tblSponsors
sponsoreid
SponsorName
11) repairs
RepairID (the product which is expected to be prepared for repair)
ProblemDescription ( broken wheel, boards etc....)
Delivery Date
ExpectedRepairDate
RepairFees
My guess is?
Using the final table list you created previously, select the Primary Keys for each table in your list. Then, select one of the tables and complete field specifications for each field. Download and use the field specifications sheet.
Note: Your field specifications sheet does not have to have the same format as the one in your text. Just be sure to provide the same information.
On each of the tables, the ID would be the Primary Key. I noticed that tblCustomers does not have a CustomerID field so I would add that and make it the Primary Key. For tblEventCodes, I'd change the EventCode to EventID to keep things consistent and make it the Primary Key.
I'll work up the field Specifications for tblSkateboard for you.
For tblSkateboard, here are the Field Specifications:
Field Name: SkateboardID
Parent Table: None
Label: SkateboardID
Shared by: None
Aliases: None
Description: Internal unique ID for Skateboard
Specification Type: Unique
Source Specification: None
Data Type: decimal
Length: 4
Decimal Places: 0
Input Mask: ####
Display Format: None
Character Support: Numbers
Key Types: Primary
Key Structure: Simple
Uniqueness: Unique
Null Support: No Nulls
Values Entered By: System
Required Value: Yes
Default Value: Automatically incremented by system, starting at 1
Range of Values: 1 - 9999
Edit Rule: Enter Now, Edits Not Allowed
Comparisons Allowed: Same Field, All
Operations Allowed: None
Field Name: SkateboardModel
Label: SkateboardModel
Description: Model of Skateboard
Specification Type: Generic
Data Type: varchar
Length: 50
Input Mask: None
Character Support: Letters, Numbers, Keyboard, Special Characters
Key Types: None
Key Structure: None
Uniqueness: Non-Unique
Values Entered By: User
Default Value: None
Range of Values: None
Edit Rule: Enter Now, Edits Allowed
Operations Allowed: Same Field, All
Field Name: Description
Label: Description
Description: Description of Skateboard
Length: 100
Null Support: Nulls
Required Value: No
Field Name: OtherDetails
Label: OtherDetails
Description: Other Details of Skateboard
Length: 2500
The original post stated to use the final table list to select primary keys for each table. I did that in the first answer.
It proceeded to state that you should select one of the tables (tblSkateboard) and complete the field specifications for each field. It stated that you didn't have to use the field spec sheet, but that you should make sure that you provide the same information. I did this in my second answer.
According to the post, all of the questions have been answered.
So I did need to do any type of database? so all of the question are answered.
I will be back tomorrow because I have to go now its evening here in Iraq. Please check tomorrow for my feedback because you did awesome work and answered the question very fast...from the rate 0-10 I will give a perfect 10. I will be back tomorrow. Thank you..
From what I saw in the request, no. It appears that they just wanted you to layout the specs for the Primary Key and for the fields for one of the tables.
You could create an Access DB, but the instructions don't specify to do so.
Enjoy!
Sr. Network Engineer
A+, MCP, MCSE, 15 years of experience
Thank you so much..you are awesome!