Importing data didn't populate related tables

[Dos Equis]

Hi all,

I am building a database in order to track all appropriate information
for my newpaper subscribers, carriers and related items.

All of my data is being pulled from an excel spreadsheet which has been
modified to hold the data in a format Access should be able to identify
including field names and data type (yes for yes/no boxes, that sort of
thing).

My primary concern at the moment is that I imported the data to the
subscriber table which has a referential integrity enforced
relationship with my yes/no table. Nothing changed in the yes/no table
while the subscriber table is full of accurate data.

I have a couple of questions I guess.

1) Do I need to have the yes/no table or is it better to leave all that
data in with the subscriber data? I should never have more than 1 entry
per subscriber on the second table so it wouldn't hurt.

2) If I leave the second table, does it need to have relationships
between each field in order to update?

3) if it does, once it's updated, can I delete the relationships and
fields from the subscriber table and still have a viable database. (I
know you don't want redundant data and that's why I would delete these
fields).

Thanks for any help you can provide.

Byron

 

[Rick Brandt]

Hi all,

I am building a database in order to track all appropriate information
for my newpaper subscribers, carriers and related items.

All of my data is being pulled from an excel spreadsheet which has
been modified to hold the data in a format Access should be able to
identify including field names and data type (yes for yes/no boxes,
that sort of thing).

My primary concern at the moment is that I imported the data to the
subscriber table which has a referential integrity enforced
relationship with my yes/no table. Nothing changed in the yes/no
table while the subscriber table is full of accurate data.

I have a couple of questions I guess.

1) Do I need to have the yes/no table or is it better to leave all
that data in with the subscriber data? I should never have more than
1 entry per subscriber on the second table so it wouldn't hurt.

If there is a one-to-one relationship a single table sounds like a better idea.

2) If I leave the second table, does it need to have relationships
between each field in order to update?

You are confused about how relationships work. They never cause insertions in
one table to automatically create insertions in another table. They can be set
up to cascade updates of foreign keys in related tables or to cascade deletion
of rows in child tables when parent records are deleted, but they never create
new records.

3) if it does, once it's updated, can I delete the relationships and
fields from the subscriber table and still have a viable database. (I
know you don't want redundant data and that's why I would delete these
fields).

If related tables are set up properly the only redundant data would be the
fields that are required to create the relationship. You would need to describe
your fields and relationships in more detail before anyone can give you a
detailed answer on that.

 

[Dos Equis]

Rick,
Thanks for your answer, I've decided to just use the one table as it is
a one-to-one relationship and this seems to simplify the data, not to
mention building forms for input. Your right, I am confused about
relationships. As I understood it, if you have table 1 and table 2,
create a relationship between table 1 ID and table 2 foriegn key with
referential integrity and cascading updates, and insert data in table
1, record 1 a record should be started in table 2 because you cascade
the data to the child table. (Table 2 is a simple yes no block). Any
way, thanks for your help

Byron