Welcome Guest ( Log In | Register )



 
Reply to this topicStart new topic
> Logic To Break Down An Access Tabbe To SQL, what is the easiest way to split this?
NilsC
post Jan 5 2005, 02:00 AM
Post #1


To Err Is Human, To Forgive Divine
Group Icon

Group: Members
Posts: 558
Joined: 24-December 04
From: http://www.ultimatekayakfishing.com/
Member No.: 1,871



I have 3 differen tables in this database that are basically repeating the same data. How can I split it up and still use it.
This is the horse project smile.gif the 3 tables are called Horse, Dam, Sire. the Horse table should be enough for all the data. (at least that is what I'm thinking) the Dam & Sire are used to track lineage and are setup Like this:

CODE
SireID; Horse; Sire; Dam; SireSire; SireDam; DamSire: DamDam; SireSireSire; SireSireDam; SireDamSire; SireDamDam; DamSireSire;DamSireDam; DamDamSire; DamDamDam; etc etc


The table is similar for the Dam, (DamId; Horse; Sire; etc etc

It's driving me nuts happy.gif

I should be able to use something like:

CODE
HorseID; Horse; SireID; DamID; DateOfBirth; Gender;


Where the SireID and DamID corresponds with a HorseID

What happens is the data are entered in the Horse(always), Sire or Dame tables when a foal is born, then the lineage is entered manually.


Is this the right way to go or should I keep 3 tables??? I guess I have a lot of hours reading this smile.gif mySQL Manual

Thanks for any tips or hints
Nils
Go to the top of the page
 
+Quote Post
miCRoSCoPiC^eaRt...
post Jan 30 2005, 08:53 PM
Post #2


PsYcheDeLiC dR3aMeR
Group Icon

Group: Admin
Posts: 2,242
Joined: 29-January 05
From: Nakorn Chaisri, Thailand
Member No.: 2,411



Try making one table in your own format:
HorseID; Horse; SireID; DamID; DateOfBirth; Gender;

All Sires and Dams would qualify for the same table. Now try breakin up other tables according to functionality..
1. Say.. maintain one table with Just the Dam ID and Damn Name
2. Another table with just Sire ID and Sire Name

Now your Dam and Sire can be referenced by using just their IDs in your main table - data redundancy can be avoided as such.

P.S. Could you be a little more clear on the Dam and Sire parts - as to what they do or what their meaning is - I'm pretty much challenged when it comes to horses and their lineage and am kind of groping in the dark. So knowing what exactly is going on would help me help you better.
.:: Cheers ::.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic

Collapse

> Similar Topics

Topics Topics
  1. Sharing Files In Windows Xp Home(15)
  2. VB6-MS Access Question(8)
  3. FTP Access: Login Failure Problems(10)
  4. VB.NET / MS Access Question(6)
  5. VB.NET: MS-Access Interaction Tutorial (Part I)(18)
  6. VB.NET & MS Access Issue(3)
  7. Connecting Ms Access To Php Using Odbc(5)
  8. Help: XP Pro Admin Account Deleted! Only Guest Access(40)
  9. Firefox 2(3)
  10. SMTP Access?(3)
  11. 4 OS On One Computer(10)
  12. C++: Basic Classes(5)
  13. Url File-access Is Disabled In The Server Configuration(7)
  14. Cracking Wireless Access Point Password?(22)
  15. Access(17)
  1. Access 97 To Access 2003(15)
  2. Can't Access Root Anymore =((5)
  3. Joomla! The Easiest Content Manager!(8)
  4. Easiest Free Forum To Create Custom Skin For?(2)
  5. Can't Access Any Site Hosted On The Server(4)
  6. Access Linux Box From Windows Machine- Putty Tool(2)
  7. Integrate Access Database Onto Intranet Site(5)
  8. Domain Name Is Not Assigned To Ip. Access Cpanel With Ip Not With Domain Name.(6)
  9. Main Trap17 Site Is Down?(0)
  10. Accessing Ms Access Database From A Centralized Location?(5)
  11. Database Access On Remote Server W/jsp(0)
  12. Access Denied As Admin On Xp, Services Troubles(4)
  13. Ssh Access ?(2)


 



- Lo-Fi Version Time is now: 30th August 2008 - 02:54 PM