Multiple Instance of Access - slow to run

[Guest]

All,

I'm using Access 2000 and, when I'm running a long query, it slows down any
other access database I have. It doesn't slow down all programs, actually,
just MS Office programs, it seems.

Is there a way to modify Access so that doesn't happen? I'd like to have the
ability to run a lengthy query on one DB, while making updates to another.

Thanks,
-Mark

 

[Jason]

I doubt it... Your using up system resources and Access is a memory hog to
begin with.

 

[Guest]

Hi Jason,

I think it's more than that (but maybe I'm wrong). While I'm running a
query, I can do other things like surf the web, check email, etc. Just runs
slower. But if I try to launch an Access db, it's almost as if the launched
db "waits" until the query is finished.

If it were simply a system resource issue, i'd expect everything to run
slower, not just other Access dbs.

-Mark

 

[Dr. Know]

Mark said:

All,

I'm using Access 2000 and, when I'm running a long query, it slows down any
other access database I have. It doesn't slow down all programs, actually,
just MS Office programs, it seems.

Is there a way to modify Access so that doesn't happen? I'd like to have the
ability to run a lengthy query on one DB, while making updates to another.

I could be wrong, but Jet (the db engine for Access) is not exactly
the most efficient multi-threaded engine out there. I fact, I would
avoid this type of usage - but that's me. Corruption of DB's is
already somewhat of a problem.
FWIW,


Dr. Know

 

[Brendan Reynolds]

My guess, for whatever it may be worth, is that you see a bigger difference
when trying to use two databases, because they are more likely to contend
for the same resources - mostly disk access. When you run a database and a
browser or e-mail client, the two apps are more likely to use different
resources at least some of the time - e.g. the database is demanding I/O
resources while the browser is demanding processor resources.

I doubt there is much you can do about it. If the data is local and you have
more than one hard disk, keeping the two databases on separate disks *might*
make some difference, but I have not tested that idea so can't say for sure.