Question on importing from Excel

[Henry Stock]

I just tried to import some data from an Excel spreadsheet (.xls) into
a new database file. One thing that troubled me about this import was
that Access import pratcially all rows and columns despite the fact that
the great majority of them were empty. This seems like a dumb default
behavior to me.

My choice on import was to try to tell it not to import those empty
columns, which I could only do one at a time, or to import them and then
delete them by atering the table design.

Likewise I did not see any options to tell it not to import empty rows,
and so it did.

What am I doing wrong?

 

[Keven Denen]

 I just tried to import some data from an Excel spreadsheet (.xls) into
a new database file.  One thing that troubled me about this import was
that Access import pratcially all rows and columns despite the fact that
the great majority of them were empty.   This seems like a dumb default
behavior to me.

My choice on import was to try to tell it not to import those empty
columns, which I could only do one at a time, or to import them and then
delete them by atering the table design.

Likewise I did not see any options to tell it not to import empty rows,
and so it did.

What am I doing wrong?

Putting empty rows and columns in your Excel file and expecting Access
to know that you really don't want those to be imported.

Why are these rows and columns blank? If you don't want them to be in
your table in Access, why don't you delete them from the Excel file?

Keven Denen

 

[Henry Stock]

Regarding empty rows and columns, I did not put them there, they ARE
there. That is what exists in a spreadsheet by default. My data starts
at cell A1 and has x columns and y rows. I have tried hiding all colums
to the right of the data and all rows below the data, but they are still
there. I have tried selecting the empty columns and deleting them, but
when you delete columns Excel fills in new columns to the right. If I
try to select all empty columns to delete them all at once, then Excel
slows to a crawl and sometimes locks up. The same things happens with
rows. Try deleting rows and Excel fills in new rows to the bottom. A
spreadsheet is always a SET matrix of cells,(255 columns by 65,536 rows)
filled or not filled. I know of no way to tell Excel to set a limit on
that. I wish I did! If you know of a way then please tell me.

I also would not have a problem if the import wizard would allow me to
select multiple columns simultaneously and tell it not to import those,
but the wizzard only allows me to select one column at a time to check
the "Do not Import" check box.

As for the second response, that is what I did because I had no option
to prevent empty rows from being imported.

I do not recall having this problem with Access 2003

I just tried to import some data from an Excel spreadsheet (.xls) into
a new database file. One thing that troubled me about this import was
that Access import pratcially all rows and columns despite the fact
that
the great majority of them were empty. This seems like a dumb default
behavior to me.

My choice on import was to try to tell it not to import those empty
columns, which I could only do one at a time, or to import them and
then
delete them by atering the table design.

Likewise I did not see any options to tell it not to import empty
rows,
and so it did.

What am I doing wrong?

Putting empty rows and columns in your Excel file and expecting Access
to know that you really don't want those to be imported.

Why are these rows and columns blank? If you don't want them to be in
your table in Access, why don't you delete them from the Excel file?

Keven Denen

 

[Clif McIrvin]

I do not recall having this problem with Access 2003

In Keven's defense, I also would have assumed that you were describing
Access importing empty cells bounded by actual data in your OP -- your
second post clarifies that point.

I also, in 2003, have never had the import / link attempt to grab rows /
columns outside (ie, to the right or below) of the extent of cells that
have been either formatted or otherwise modified.

Not having 2007 (with your reference to 2003, I assume you are
discussing 2007 ... please confirm to the group), I cannot speak to the
issue you describe.