database records

[Bob Quintal]

i have a database of about 5000 records. how do i take out the
old ones and store them so they are retreivable, but not in the
same database as currently being used, as it is slowing the
database down.

just 5000 records? there is something else causing the slowdown.
Perhaps you are sorting the table in your form but have not made an
index in the table that brings up the sort?

I've tables with over 300,000 records that are lightening fast.

To reply to your question, you use an append query that adds the
records meeting certain criteria to the new table (in your case, the
age of the record, or a value that says completed), then you use a
delete query on the local table that deletes the records using the
same criteria.

 

[kdkelch]

i have a database of about 5000 records. how do i take out the old ones and
store them so they are retreivable, but not in the same database as currently
being used, as it is slowing the database down.

 

[Larry Linson]

i have a database of about 5000 records. how do i
take out the old ones and store them so they are
retreivable, but not in the same database as currently
being used, as it is slowing the database down.

As Tom said, you really have to work at doing things wrong to have
performance problems with as few as 5,000 records.

Review the performance tips in MVP Tony Toews' site at
http://www.granite.ab.ca/accsmstr.htm.

Larry Linson
Microsoft Access MVP

 

[kdkelch]

Thank you for your response. However, if only 5,000 records is not that
much, than why is our system so slow when we do searches? This should be
relatively fast considering we're on a company server, correct?

 

[Douglas J. Steele]

What speed LAN connectivity do you have to your server? Do you have your
application split into a front-end (containing the queries, forms, reports,
macros and modules) linked to a back-end (containing the tables) with only
the back-end on the server?

 

[Bob Quintal]

Thank you for your response. However, if only 5,000 records is
not that much, than why is our system so slow when we do searches?
This should be relatively fast considering we're on a company
server, correct?

"Bob Quintal" wrote:

Doug Steele asks you some good questions about the server, If it's a
slow ethernet, or overloaded, things will be slow. If the database
is not properly indexed, things will be slow.

You are better off to fix the root cause of the problem rather than
a band-aid, since band-aids are only a temporary solution.