Importing more than 256 rows

[Guest]

I have a .csv file that contains more than 256 rows. Is
there a way to import the first 256 rows into one table,
and then import row 1 and rows 256-510 into a second
table, and link them using row 1 as the relationship?

 

[Douglas J Steele]

I don't understand what you mean by "link them using row 1 as the
relationship".

If you've got two tables, you link them through a field (or fields) in each
row in both tables, not through a specific row.

 

[John Vinson]

I have a .csv file that contains more than 256 rows. Is
there a way to import the first 256 rows into one table,
and then import row 1 and rows 256-510 into a second
table, and link them using row 1 as the relationship?

Do you mean 256 *columns* perhaps? There is no limit on the number of
rows that you can import.

If you do in fact mean columns, then I know this can be done, but it
won't be easy. I am not certain whether you can use customized text
import to skip 255 columns; you might instead have to write VBA code
to open the file and parcel its data into recordsets.

In any case, a one-to-one Query is still limited to 255 fields. You
will need to construct a properly normalized set of tables (with
multiple records rather than multiple fields for the repeated fields
which almost surely exist in your file) and migrate the data into
these tables.

John W. Vinson[MVP]

 

[Mike Painter]

I have a .csv file that contains more than 256 rows. Is
there a way to import the first 256 rows into one table,
and then import row 1 and rows 256-510 into a second
table, and link them using row 1 as the relationship?

If you mean columns the answer is probably not.
I'd guess that a table with 510 fields in it has about zero chance of being
of any use in a relationa data base.
If you have columns that repeat, Monday, Tuesday,....Sunday or
things like date1, date2,date3
you should either stick with Excel or normalize the tables.

 

[Douglas J Steele]

If you mean columns the answer is probably not.
I'd guess that a table with 510 fields in it has about zero chance of being
of any use in a relationa data base.
If you have columns that repeat, Monday, Tuesday,....Sunday or
things like date1, date2,date3
you should either stick with Excel or normalize the tables.

I believe Excel has a 255 column limit as well.