Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-access > #13573
| From | Neil <neil@myplaceofwork.com> |
|---|---|
| Newsgroups | comp.databases.ms-access |
| Subject | Re: Way to identify open processes? |
| Date | 2019-04-03 10:00 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <q82e9o$3pb$1@dont-email.me> (permalink) |
| References | <q822qq$c7$1@dont-email.me> <0c3bbfb2-69b1-4b28-ba89-2e291eca11da@googlegroups.com> |
On 4/3/2019 8:07 AM, Ron Paii wrote: > On Wednesday, April 3, 2019 at 5:44:46 AM UTC-5, Neil wrote: >> 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 >> on completion. >> >> Is there a way to identify processes that are running and accessing the >> database, thus interfering with other routines? >> >> -- >> best regards, >> >> Neil > > if you have Microsoft's sysinternalsSuite on your workstation, the psFile program can list all log-in Names with a file open. If the BE is on a server, you will need admin rights to run it. I send the results to a text file for review, psfile outputs to the terminal. > > open a command prompt with admin rights to the folder containing the file > move to the folder with psfile program. > psfile "Full Path and name to the BE file" > outputfile.txt > notepad outputfile.txt > > Output looks like the following > > Files opened remotely on ServerName matching "Full Path and name to the BE file" > > [1946157101] "Full Path and name to the BE file" > User: LoginNameOnServer > Locks: 22 > Access: Read Write > [-2013265801] "Full Path and name to the BE file" > User: LoginNameOnServer > Locks: 18 > Access: Read Write > [1342177404] "Full Path and name to the BE file" > User: LoginNameOnServer > Locks: 24 > Access: Read Write > Thanks, this looks interesting. If the required admin rights are at the same level as FTP or login credentials, maybe this could work. It's worth looking into. The routine in this case replaces the database, but doesn't require functional access to it. So, another thought I had was having a way to pause all processes accessing the database until the routine was completed, then allow those processes to resume. Any ideas would be welcome. -- best regards, Neil
Back to comp.databases.ms-access | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Way to identify open processes? Neil <neil@myplaceofwork.com> - 2019-04-03 06:44 -0400
Re: Way to identify open processes? Ron Paii <ron81pai@gmail.com> - 2019-04-03 05:07 -0700
Re: Way to identify open processes? Neil <neil@myplaceofwork.com> - 2019-04-03 10:00 -0400
Re: Way to identify open processes? Ron Paii <ron81pai@gmail.com> - 2019-04-03 10:41 -0700
Re: Way to identify open processes? Neil <neil@myplaceofwork.com> - 2019-04-03 15:54 -0400
Re: Way to identify open processes? Ron Paii <ron81pai@gmail.com> - 2019-04-03 13:58 -0700
csiph-web