Importing and big tables with over 65K of records

  • Thread starter Thread starter Gabe
  • Start date Start date
G

Gabe

Hello folks,

I am working on a project to assemble a bunch of excel
spreadsheets into one big database table that I can query
and leverage for marketing purposes. I started assembly,
importing spreadsheets, and cutting and pasting. The
wierdest thing happened around 65K of records, Access
won't let me import anymore or cut and past anymore. I
don't think that it is a RAM issue because it happened
with Excel as well. Do Excel and Access allow files with
more than 65,000 records...I think so. Why can't I import
anymore? I know people get more than 65k records into
excel, I have seen spreadsheets with more than that. How
do I get my job done? I really need to have one big table
or spreadsheet. Please help me!!! :(
 
Two Questions:
1) Have you tried compacting the database - it may help
2) Do you get an error message? If so, what is the error?

Access can easily handle large numbers of records.

Scott Shearer, MCSD, MCDBA

msshearer@ @ @ hotmail.com

----- Gabe wrote: -----

Hello folks,

I am working on a project to assemble a bunch of excel
spreadsheets into one big database table that I can query
and leverage for marketing purposes. I started assembly,
importing spreadsheets, and cutting and pasting. The
wierdest thing happened around 65K of records, Access
won't let me import anymore or cut and past anymore. I
don't think that it is a RAM issue because it happened
with Excel as well. Do Excel and Access allow files with
more than 65,000 records...I think so. Why can't I import
anymore? I know people get more than 65k records into
excel, I have seen spreadsheets with more than that. How
do I get my job done? I really need to have one big table
or spreadsheet. Please help me!!! :(
 
Hi Gabe,

You can't get more than 65536 rows into an Excel worksheet. But there's
no limit on the number of rows you can have in an Access table (at least
until you hit 1GB or 2GB limit on the size of the mdb file).
 
The only thing I can think of is that your table structure is excluding
duplicates... have you checked this? I assume the number of columns are the
same?

HTH.

Tom.
 
Back
Top