Making a master table

[Srin]

I have three tables that contain different columns but linked by a primary column call Name. I want to create a table where all these different columns in the three tables join to form a master table which can be updated regularly either through the master table or the smaller tables. The master table also has the primary column as Name.


If I update the master table with records, it should update the respective linked table and vice versa.
I also want to link these tables to my SharePoint site.

Note: except the Name column, none of these tables have any other columns in common
How do I go about this?

[June7]

Name is a reserved word. Should not use reserved words as names. Names make poor unique identifiers. What if you have multiple John Smith? Also, text is supposed to be slow performer for indexing.

Don't need a 'master' table. Use queries to display related info. Use form/subform arrangements for data entry/edit.

Provide data schema for analysis. What is relationships of these tables: 1-to-1, 1-to-many, many-to-many?

[Srin]

I want to have a Master table because, I won't be entering data by the record. I will be copying data worth 100s of rows/records. Also its not actually a name. Its an ID

Also assume I am a noob, and pls give an example of what queries to use. I am new to access but can do basic queries.

[June7]

I don't understand why that calls for a 'master' table. What you describe will require SQL action queries (UPDATE and INSERT) to keep the tables synchronized.

Simple SELECT queries with JOIN clauses can display related data. Use the query builder to construct.

Did not provide info about relationships.

[Srin]

Could you give me an example query for the problem description above. Thank you

[June7]

I don't know data structure and relationships. Don't even know why you have 3 tables instead of 1 to begin with. Can't help until you provide requested info. If you want to provide db for analysis, follow instructions at bottom of my post.

[orange]

srin,

Please give us the plain English description of WHAT you are trying to do. Keep it in simple English, no Access jargon until we understand the "business" involved. June asked why you currently have 3 tables -- I'd like to know why, also.

[Srin]

I used the same scenario as @June7 suggested and it worked fine. I had little knowledge of queries before but this helped. Thank you