Is it possible to import Excel sheet into multiple Access tables

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

Guest

I had a spreadsheet that grew out of control, so I decided to build an Access
database to accomodate (my first use of Access). I have always heard that
multiple tables are more efficient than one, so I built out the DB with about
8 different tables, matching the field names between Excel and Access. When
I went to Import the Excel sheet, I discovered that the data would be
populated into ONE table, not all. Is there a way to populate records across
multiple tables from a single spreadsheet?
 
I had a spreadsheet that grew out of control, so I decided to build an Access
database to accomodate (my first use of Access). I have always heard that
multiple tables are more efficient than one, so I built out the DB with about
8 different tables, matching the field names between Excel and Access. When
I went to Import the Excel sheet, I discovered that the data would be
populated into ONE table, not all. Is there a way to populate records across
multiple tables from a single spreadsheet?
Click to expand...

why do you need to separate the columns into different tables? The
only reason to do this in Access are (1) if the columns describe
different entities; (2) you have too many columns for a single
table...
 
You can import into one table, then use Append queries to add the specific
fields to the tables. You'd need an append query for each of the tables.
Query the new table you imported to, save it as an append query, then select
the fields from the table in the query design grid that you want appended.
When you select append query, Access will ask you which table you want to add
the records to. This is where you choose the table for the fields that will
be added in that query.
 
You can import named ranges from excel one at a time if that is easier for
you than multi-queries.
Pete
 
Really? I know it's been several years but you asked this question:


why do you need to separate the columns into different tables? The
only reason to do this in Access are (1) if the columns describe
different entities; (2) you have too many columns for a single
table...

He explained in precise detail WHY he needed several tables. Another useless forum. Sorry.
 
Back
Top