Maximum database size?

[Coleen]

Is there a size limit to Access 2000 Databases? I have a database that has
over 40,000 records. Ordinarily I wouldn't think that was a problem, but I
ran a query on two imported tables (I have to find duplicate records, and
append the un-matched records from one table to the other) I run the query
just fine, but when I try to go to the end of the query to find out how many
records I have, Access completely locks up! I've done this 3 times, and
each time it locks up and when I go to task manager it shows Access is not
responding and I have to close it and Try again. Any suggestions as to what
could be causing this? TIA,

Coleen

 

[Rick B]

Read the help files. Type in "specifications".

 

[Coleen]

Thanks, but that wasn't my main question...although I did ask what the
maximum size is, what I'm concerned about is WHY the db keeps locking up
when I try to access the query on this table! 40,000 records shouldn't be a
problem - I've had this type of problem before when running queries...I can
create the query and run it just fine, but when I try to scroll through the
data or go to the last record, it locks up! If anyone has a suggestion
about THAT problem, I would appreciate any help...

Thanks!

 

[mnature]

I have a somewhat old, slow computer. I find that I need to allow it a
little time to finish doing whatever computations it is doing, before I start
trying to move around a query. What I look for, to see if the computations
are done, is that the number of records shows up at the bottom of the query
window. It's also a quick and dirty way to see if my query did what I
thought it would do, since I usually know about how many records I should see
displayed.

 

[Brendan Reynolds]

The fact that Task Manager says Access is 'not responding' does not really
mean anything. Task Manager will report this when Access is busy executing
the query, and would actually complete the operation and resume responding
if given time. How long have you waited for Access to finish processing the
query?

The number of records is not the only factor determining how long the query
will take. The complexity of the query (multiple joins, complex expressions,
sorting on non-indexed fields) also plays a significant role. If you post
the SQL for the query, and indicate what indexes exist, someone may be able
to advise on possible optimizations.

 

[Coleen]

Thanks for the responses - I should probably post to the query group, but I
never do get an ending row number, and I have let the query run for about 5
minutes (I have a new computer - only about 6 months old) so I don't think
speed is the issue and the query is just from a generic find unmatched
wizard...the query runs, I just can't scroll through the data! That's why I
thought it was a database issue...

Oh well, I re-started my computer, created a new database (imported the
data) and created my own un-matched query and it works just fine - go
figure!

Thanks!