|Subject:||Way to identify open processes?|
|Posted by:||Neil (ne…@myplaceofwork.com)|
|Date:||Wed, 3 Apr 2019|
I have a problem with a routine that fails with an on-line Access
database, giving the error that the routine can't run because there is
another process running. The problem originated after
converting/updating the Access database from .mdb to .accdb form.
I verified that all process calls in my routines are closed and removed
Is there a way to identify processes that are running and accessing the
database, thus interfering with other routines?