N
nullGumby
Running MSA2K3.
I have this problem a lot. I have an MDB open and I run a query. It
uses up most of my CPU, but I'm still able to open and work in other
applications (IE, Lotus Notes, whatever). However, if I try to open
another MDB, it doesn't seem to open until the other MDB finishes
processing. If I enter debug mode in MDB #1, then MDB #2 opens right
up.
What I think is happening is when I open MDB #2, Windows/Access sees
there's another instance of Access running, so it uses the first
instance to load the MDB--instead of just starting another instant of
Access.
Has anyone experienced this problem/know how to change this behavior?
Thanks.
I have this problem a lot. I have an MDB open and I run a query. It
uses up most of my CPU, but I'm still able to open and work in other
applications (IE, Lotus Notes, whatever). However, if I try to open
another MDB, it doesn't seem to open until the other MDB finishes
processing. If I enter debug mode in MDB #1, then MDB #2 opens right
up.
What I think is happening is when I open MDB #2, Windows/Access sees
there's another instance of Access running, so it uses the first
instance to load the MDB--instead of just starting another instant of
Access.
Has anyone experienced this problem/know how to change this behavior?
Thanks.