How many records is too many

[sambo]

I am creating a database to log Quality Assurance data. Every unit that is inspected will have around 35 records in the "Master Inspection" table.
If there are approx. 100 units inspected per day, that means 3500 new records per day in the table.
5 days a week means roughly 15,000 records a week.
4 weeks a month means 60,000 records a month.
This table is growing very rapidly.
How badly will this hurt when generating Reports or Queries from this table? Is there a good way to deal with this over-population problem?

 

[pdx_man]

Migrate to SQL Server or Oracle. Link the tables into Access.

 

[sambo]

Ah pdx_man... Always a pleasure to hear from a fellow Oregonian.

Would switching to SQL Server 7 help to make searches faster? Does SQL also have the capability to hold infinitely more records than a simple Access App? How hard is it (in hours please) to make the switch over?
I am assuming the answer to both of these questions is yes..

 

[pdx_man]

Gotta love the rain, eh?!

The answer is Yes. And where the power really begins to kick in is when you write stored procedures in SQL and then create a pass-through query in Access to get the results. Just last week I re-wrote an Access query that normally ran 30 minutes. Using the Stored Procedure, it now runs in 25 seconds. This is a massive database where some tables are in excess of 4 million records. The benefits of migrating to a Server back-end are numerous.