Data Extraction/update

[Steven.Allman]

I have another strange problem
My corporation has 13000 employees
I maintain data on about 500 that are qualified to do a certain task.
I finally got access to the personal data on ALL employees, but my queries take FOREVER to run on all 13000 records. Can I create an update to simply pull the data for my 500 into my own data base, while not loosing the 'other' data I have for those records.
Company DB has 140 fields, I only need the data from 9-10
my DB has 30 fields.


Just pretend its guys updating there phone number with HR, but they are not letting me know, so I need to pull from HRs data and update mine, but I want to do it with one simple query, or form.. Anyone know how I would go about this?

[TheShabz]

1. Link to their table
2. run an update query on your table, joining on the employeeIDs of the linked table, that updates the information you need.

Also, your queries should not take long for 13k records, anyway. You might want to spend some time figuring out why that is. I regularly query multiple tables of 5million+records in a matter of a a couple minutes. 13k records should be a matter of seconds.

[Steven.Allman]

The query length is due to network linked table, not really record numbers
How do I setup the Parent table, I don't want to create new records, and I don't want to update HR with MY old info. I have never done update queries

[TheShabz]

Ok. Let's call your table myTable and the linked HR table hrTable. The fields in your table you want to update are m1, m2, and m3. The fields from the HR table that you want to pull the info from are h1, h2, and h3.

UPDATE myTable INNER JOIN hrTable ON myTable.empID = hrTable.empID
SET myTable.m1 = hrTable.h1, myTable.m2 = hrTable.h2, myTable.m3 = hrTable.h3;

That updates your table's m1, m2, and m3 fields with the corresponding data in hrTable's h1, h2, and h2 fields joined on the empID which is a unique identifier to ensure that the proper records are being updated. if empID is not available you will have to find some way of uniquely identifying each record.

[Steven.Allman]

That was not as scary as I thought it would be. Thanks