table relationships

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am managing a project and have multiple spreadsheets (originally in Excel
that were imported into Access) all of which share a common field. How do I
set up a relationship between all the spreadsheets so as to ensure that if I
update a common field in one spreadsheet it will automatically update the
same field in all the other spreadsheets? I assume there is a way to do this
and that not every database is based strictly on one super huge spreadsheet
with hundreds of columns. I'm so frustrated with this. Please help!
Thanks!!!
 
U can set relationship through Tools -> Relationships.

But try to use this key as a primary key in one table. and foreign key in
other tables. In such a situation if table 'A' has field 'ID' as primary key
and 'B' 'C' 'D' use same 'ID' as foreign key. U may write a code to append or
update the respective tables. U require to write a very customised code to do
all permudation combinations from same set of code or may also do same with
individual set of vb code.
 
Do you really mean to set up relationships between "spreadsheets"? I think
you need to start thinking about relationships in tables.

You haven't provided any information about your tables, fields, records, ...
 
I highly suggest getting some relational database training or reading
"Database Design for Mere Mortals" by Hernandez before proceeding any further
on this database.
 
If you have worked with spreadsheets, you will have to relearn everything you
think you know about data management.

Microsoft has a nice condensation of information about normalizing a database:

http://support.microsoft.com/kb/283878/EN-US/

You could think of normalization as being done in steps, with these steps
being called First Normal Form, Second Normal Form, Third Normal Form.

For First Normal Form, you create a separate table for each set of related
data. So, if you have customers, products, and orders, you would create a
table for each of those topics, and only have data that relates to that topic
in that table. You then uniquely identify each set of data within these
tables with a primary key. Finally, eliminate any repeating groups in the
individual tables. For instance, if you have fields that are named Vendor
Code 1, Vendor Code 2, and Vendor Code 3, then you need a separate table
called Vendors which will be linked back to your original table with a
foreign key.
 
What you will need to do is have primary keys in each table. First i
would sit down and look at the tables and see what the primary keys can
be. You want them to be unique. Once you do that i suggest researching
access relationships because they can be tricky.
 
Back
Top