Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS Access......USING relations to populatle fields

Status
Not open for further replies.

Professor0210

Technical User
Mar 20, 2004
2
US
I'm out here in Baghdad, new to Access, without manuals needing to use Access to perform a task. I need to populate certain fields on one table with fields from another table.

I've learned how to set up a relationship, but that's it. How do I fillin a userid in one table and get the user's info filled in on this table with info from another table?

Is that clear as mud?

Thanks.
 
quick answer is you don't unless absolutely necessary. you don't need to store the same information in two tables.

can you be a bit more specific in what you are looking to do?

Jamie Gillespie
j-gillespie@s-cheshire.ac.uk
 
Firstly relationships don't really do anything, so don't expect any help there.

Bring the two tables into to the Graphical Query-by-Example Screen. If your relationships haven't pre-drawn a join line between the userid fields in each table then do so now.

Select all the fields that are either going to receieve data or are going to provide it. Press the button and see if everything looks right.

Now change the query to an update query (using the toolbar). Now for each field you want loading, put the name of the corresponding provider field into the update line eg if newtable.haircolour is going to be loaded from oldtable.hcol then put [oldtable.hcol] under [newtable.haircolour].

That's it really. Make sure you take a back-up of your database before you do major updates.


 
What we're trying to do is use Access to create a ticketing system for trouble calls. one table for the actual work tickets, one table for the user data information.

 
BNPMike said:
Firstly relationships don't really do anything, so don't expect any help there.

I disagree, relationships are very important.

JGillespie's assessment seems to be accurate.
Add the UserID field to the WorkTicket table.

To view all of the information in a report, create a query to show you the information about the person on the work order.

Good luck


-Gary
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top