Home » Developer & Programmer » Designer » Effective Database Design
Effective Database Design [message #134622] Thu, 25 August 2005 15:53 Go to next message
poratips
Messages: 345
Registered: April 2005
Location: IL
Senior Member
Hi,
I like to know that how can I make the good design for my new existing form which one user going to fill out?
I need following fields.
Could u pl. let mek now how I can design?
Should I design table for each Registrant, Co-Registrant and Future Address in a different table?
Or just only one big table? This table(s) will be affected by web application where user will make the registration.

Field Name Description
ID gift registry number for this record
Receive_Email Status of the record for email N , O , I
Reg_FName Registrant First Name
Reg_LName Registrant Last Name
Reg_Address1 Registrant Address 1
Reg_Address2 Registrant Address 2
Reg_City Registrant City
Reg_State Registrant State
Reg_Country Registrant Country;
Reg_Postal Registrant Postal code
Reg_Phone1 Registrant Phone
Reg_Phone2 Registrant Phone
Reg_Phone3 Registrant Phone
Reg_Email Registrant Email
Reg_Role Registrant Role Drop down of Bride, Groom, Partner and Other
Reg_Role_Other Registrant Role free form field if Other is selected
Co-Reg_FName Co-Registrant First Name
Co-Reg_LName Co-Registrant Last Name
Co-Reg_Address1 Co-Registrant Address 1
Co-Reg_Address2 Co-Registrant Address 2
Co-Reg_City Co-Registrant City
Co-Reg_State Co-Registrant State
Co-Reg_Country Co-Registrant Country
Co-Reg_Postal Co-Registrant Postal code
Co-Reg_Phone1 Co-Registrant Phone
Co-Reg_Phone2 Co-Registrant Phone
Co-Reg_Phone3 Co-Registrant Phone
Co-Reg_Email Co-Registrant Email
Co-Reg_Role Co-Registrant Role Drop down of Groom, Bride, Partner and Other
Co-Reg_Role_Other Co-Registrant Role free form field if Other is selected
Event_Date Event Date
Event_Type Select type of event from drop down offering options of Wedding, Commitment Ceremony, House Warming, Holiday, Graduation, Birthday, Other
Event_Type_Other Event Type free form field if Other is selected
Retailer_1 Select Retailer 1from List;
Retailer_1_Other Retailer 1 free form Other
Registry_Number_1 Registry number at Retailer 1 selected
Registry_Password­_1 Guest password at Retailer 1 selected
Retailer_2 Select Retailer 2from List; selections include Attachment A
Retailer_2_Other Retailer 2 free form Other
Registry_Number_2 Registry number at Retailer 2 selected
Registry_Password­_2 Guest password at Retailer 2 selected
Retailer_3 Select Retailer 3from List; selections include Attachment A
Retailer_3_Other Retailer 3 free form Other
Registry_Number_3 Registry number at Retailer 3 selected
Registry_Password­_3 Guest password at Retailer 3 selected
Product_Style_1 Product Style chosen from a checklist
Product_Style_2 Product Style chosen from a checklist
Product_Style_3 Product Style chosen from a checklist
Product_Style_4 Product Style chosen from a checklist
Product_Style_5 Product Style chosen from a checklist
Product_Style_6 Product Style chosen from a checklist
Product_Style_7 Product Style chosen from a checklist
Product_Style_8 Product Style chosen from a checklist
Product_Style_9 Product Style chosen from a checklist
Product_Style_10 Product Style chosen from a checklist
Source Source where record came from or where couple heard about the offer include: Retailer; Magazines, Show or Event, Online Wedding Site, David’s Bridal, Other
Source_Other Source free form field for Other option
Create_Date Date the record was created in the file
Promo_Code Promotion code as submitted on forms or online
Registry_Sub_Status Registry Submission Status; options include Submitted, Sent, or Denied
Registry_Sub_Date Registry Submission Date as defined by date submitted online or by date reported by Print All
Registry_Sent_Date Registry Sent Date is the date the gift was sent by Print All
Registry_Value Value of product registered for as defined by amount couple submitted online or amount reported by Print All; Note: if amount reported by Print All differs, override with Print All data; format as 5N.2N eg, $12345.00
Completion_Sub_Status Completion Submission Status; options include Submitted, Sent, or Denied
Completion_Sub_Date Completion Submission Date as defined by date submitted online or by date reported by Print All
Completion_Sent_Date Registry Sent Date is the date the gift was sent by Print All
Registry_Sales Sales of Calphalon product as reported by Print All; format as 5N.2N eg, $12345.00

Move_Date Date Future Address will become effective
Fut_FName Future First Name
Fut_LName Future Last Name
Fut_Address1 Future Address 1
Fut_Address2 Future Address 2
Fut_City Future City
Fut_State_Province Future State_Province
Fut_Country Future Country
Fut_Postal Future Postal codel
Fut_Phone1 Future Phone
Fut_Phone2 Future Phone
Fut_Phone3 Future Phone
Fut_Email Future Email
Email_Last_Date Last date registry was send email communication
Email_Last_Subject Last email communication subject line
Comments Comments field that can be added to, but not replaced
Incentive_Reg_Email_Date Date that email is sent to database users with event dates prior to 6 months.
Incentive_Comp_Email_Date Receive this email if haven’t already received this email, Registry_Sub_Date is null, AND Event_Date is between Now() and (Now()+6 months)
Date that email is sent to database users with event dates occurring 1 to 2 months ago.
Receive this email if haven’t already received this email, Completion_Sub_Date is null, AND Event_Date is between (Now()-30 days) and (Now()-60 days)
Re: Effective Database Design [message #134773 is a reply to message #134622] Fri, 26 August 2005 15:56 Go to previous message
poratips
Messages: 345
Registered: April 2005
Location: IL
Senior Member
still waiting for response
Previous Topic: mini Oracle Project
Next Topic: TOOL for Oracle Lite
Goto Forum:
  


Current Time: Thu Oct 23 00:58:57 CDT 2014

Total time taken to generate the page: 0.06093 seconds