Transferring Data

[J]

I have a small dilemma. I have a "JOB" and "STATUS" table. There are
3 fields in the status table that I need to bring over and drop into
the corresponding column in the job table. I need to make it so that a
"project number" in my status table matches up with a "project number"
in the job table so that when the data is transferred, the values will
all go into the correct positions.

I have an update query started but I'm not sure if I'm going about my
problem the right way. So far here is what I have:

Field: DWG No Rev No
Table: Job Card Job Card Job Card
Update To:
Criteria: Is Null Is Null Is Null

Any help regarding this problem would be greatly appreciated

 

[Rick B]

Why would you want to copy this data to the other table? Just relate the
two tables, then you can pull data from both tables into your forms,
queries, and reports.

If you try to take data from related tables and combine it all into one
table, then you are most likely "unnormalizing" your database. The whole
point of a relational database is to have data stored in various tables and
to RELATE the tables to each other.

Please provide more details if I misunderstand your post.

 

[J]

I see where you're coming from when you ask why I would want to copy
the data. The 2 tables are related but when the data is being copied
over, most of it will be going into a new column. I'm doing this
database for someone else and this is how they said that they wanted
it. If there's anything I havn't included to help fix my problem,
please let me know so I can post the information.

 

[Rick B]

Again, why would you do this? Are they actually working in the tables? If
so, they should not be. If they want to see data from more than one table,
then they should be in a query, report, or form. If they have you building
this for them, then obviously they do not know how to create a proper Access
database. Don't let them tell you how to build it , just what they want the
end results to be.

If their goal is to see the data from both of those tables, then a query or
report is needed. If their goal is to pull up a record with data from
multiple one-to-one relationship tables and be able to edit it, then a form
is needed.

One other issue with what they want to do. It would be redundant and lead
to data corruption. What if they need to change one of those values that
you have "copied" to the new table? Will they remember to change it in BOTH
tables? I doubt it.

In short, don't get bogged down with them on how to build it - that's your
job. Just find out what they want to accomplish, and then build the
database to accomplish those tasks using proper database design concepts.
Also keep in mind, your users should NEVER see/touch the tables. Tables are
not user-interfaces. The users should be interfacing with your database
primarily using forms and reports.