Exporting more than 65'536 rows from Access to Excel

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

Guest

I have an Access database which currently has over 65'536 rows in it. I need
to export this into an Excel file every month, but as it cuts off at 65'536
rows, I just want to keep the newest records which come under a heading in
the database called 'date input'.
I've tried sorting by the heading 'date input' in Access but when its
exports to Excel it jumbles all these up.

Is there a way of only exporting the top 65'536 rows in the 'date input'
column?
Any advice would be most welcome, sorry if I havent explained it very well.
I'm new to Access (as if you couldnt guess!).
 
While you can use TOP 65536 in an SQL Select statement, that doesn't handle
ties, so it may in fact try to export more than 65536 rows of data.

Let's step back a bit, though.

What exactly is the data? Do you need to export everything ever month, or.
for example, would exporting only records for the previous month be
sufficient?

If only previous month data is sufficient, when are you going to be running
this: in the month following, or at the end of the month you want exported?
(What I'm trying to get at is that you can automate the selection criteria,
but we need to know your requirements in order to do that)
 
Hi Douglas,
I would need to export the whole database each month if possible, not just
one month. The data includes dates of birth, names, postcode, date entered
into database etc.
Thanks for your help.
 
Excel isn't a reporting tool

Try Crystal Reports or something similiar; it doesn't have a limit at
65535 rows
Lol

Sorry; but any use of spreadsheets anywhere is by definition--
inefficient

-Aaron
 
I'm confused, then, as to why you're asking about only exporting the top
65536 rows.
 
Sorry, not explaing myself well. When I export my database into Excel it
cuts it off at the max no. of rows Excel can hold. I wanted to see if there
was a way of only export the newest rows, as at the moment it jumbles them up.
 
You're right that you're not explaining yourself well! <g>

Do you datestamp the entries in the table so that you know which are the
newest?
 
Back
Top