If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
populating table fields
I'm trying to populate fields in one table with data from another
say I have a table with employees in as follows employeeID(primary key) name charge rate trade and say a table called labour LabourID(primary key) job record name (selected on a lookup to the employee table) charge rate (populated data from employee table once name had been picked) trade (populated data from employee table once name had been picked) Any help would be great Mike |
#2
|
|||
|
|||
On Mon, 14 Mar 2005 14:45:07 -0000, "Mike"
wrote: I'm trying to populate fields in one table with data from another say I have a table with employees in as follows employeeID(primary key) name charge rate trade and say a table called labour LabourID(primary key) job record name (selected on a lookup to the employee table) charge rate (populated data from employee table once name had been picked) trade (populated data from employee table once name had been picked) You're missing the point of how relational databases work. They're based on the "Grandmother's Pantry Principle" - "a place - ONE place! - for everything, everything in its place". The Labour table should contain the EmployeeID as a link to the Employee table - AND NOTHING ELSE from the Employee table. Storing the name, the charge rate, or the trade redundantly is neither necessary nor beneficial. If (as it appears likely) you're trying to enter data directly into the Labour table datasheet - don't. Table datasheets are of VERY limited value for anything other than design and debugging. Instead, create a Form based on Employees, with a Subform based on the virtuous and loyal labour of the horribly exploited workers... oops, my politics are showing... John W. Vinson[MVP] |
#3
|
|||
|
|||
Thanks for that
will change the way it works regards Mike "John Vinson" wrote in message ... On Mon, 14 Mar 2005 14:45:07 -0000, "Mike" wrote: I'm trying to populate fields in one table with data from another say I have a table with employees in as follows employeeID(primary key) name charge rate trade and say a table called labour LabourID(primary key) job record name (selected on a lookup to the employee table) charge rate (populated data from employee table once name had been picked) trade (populated data from employee table once name had been picked) You're missing the point of how relational databases work. They're based on the "Grandmother's Pantry Principle" - "a place - ONE place! - for everything, everything in its place". The Labour table should contain the EmployeeID as a link to the Employee table - AND NOTHING ELSE from the Employee table. Storing the name, the charge rate, or the trade redundantly is neither necessary nor beneficial. If (as it appears likely) you're trying to enter data directly into the Labour table datasheet - don't. Table datasheets are of VERY limited value for anything other than design and debugging. Instead, create a Form based on Employees, with a Subform based on the virtuous and loyal labour of the horribly exploited workers... oops, my politics are showing... John W. Vinson[MVP] |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
unable to repair inobox | Sudheer Mumbai | General Discussion | 1 | February 20th, 2005 11:55 AM |
Get data from combo box to popluate the next box | Lin Light | Using Forms | 4 | December 30th, 2004 05:01 PM |
Update - If statement | Dan @BCBS | Running & Setting Up Queries | 13 | December 14th, 2004 06:02 PM |
Automatic filling of fields in table two from table one | Jim Kelly | Database Design | 1 | September 27th, 2004 10:16 PM |
Name not showing ID is | René | Setting Up & Running Reports | 11 | June 29th, 2004 01:40 AM |