MSACCESS.EXE does not stop after exiting Access 2003 mcglincym 31.08.2006 19:18:01 Occasionally, the MSACCESS.EXE process does not stop after I exit Access. The process shows about 50% CPU usage in Windows Task Manager. Sometimes memory usage increases slowly but not always. As far as I can tell, there is nothing going on before I exit.

Re: MSACCESS.EXE does not stop after exiting Access 2003 "Chris Mills" <phad_nospam[ at ]cleardotnet.nz> 01.09.2006 03:54:44 I presume you mean "stays on the taskbar". Various programming "bugs" (actually I think they are Access bugs) can cause this, and they can be a right pig to find. See: http://www.mvps.org/access/bugs/bugs0005.htm Also (I don't see it listed there) I'm under an impression that: If Something Then ....instead of... If Something = True Then ....can cause this bug. Or some bug. (well, I'm thinking back to A97 whatever) Chris "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message news:A723CE8A-6747-4BDC-9739-A58606A3576E[ at ]microsoft.com... [Quoted Text] > Occasionally, the MSACCESS.EXE process does not stop after I exit Access. The > process shows about 50% CPU usage in Windows Task Manager. Sometimes memory > usage increases slowly but not always. As far as I can tell, there is nothing > going on before I exit.

Re: MSACCESS.EXE does not stop after exiting Access 2003 mcglincym 01.09.2006 13:19:02 Access does not show on the taskbar, only under Task Manager. Also, I usually close an open database before exiting Access and some of my databases do not include any code at all. I'll read the reference. "Chris Mills" wrote: [Quoted Text] > I presume you mean "stays on the taskbar". > > Various programming "bugs" (actually I think they are Access bugs) can cause > this, and they can be a right pig to find. > > See: > http://www.mvps.org/access/bugs/bugs0005.htm > > Also (I don't see it listed there) I'm under an impression that: > If Something Then > ....instead of... > If Something = True Then > ....can cause this bug. Or some bug. > (well, I'm thinking back to A97 whatever) > > Chris > > "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message > news:A723CE8A-6747-4BDC-9739-A58606A3576E[ at ]microsoft.com... > > Occasionally, the MSACCESS.EXE process does not stop after I exit Access. > The > > process shows about 50% CPU usage in Windows Task Manager. Sometimes memory > > usage increases slowly but not always. As far as I can tell, there is > nothing > > going on before I exit. > > >

Re: MSACCESS.EXE does not stop after exiting Access 2003 "Douglas J. Steele" <NOSPAM_djsteele[ at ]NOSPAM_canada.com> 01.09.2006 16:50:51 You're not doing anything funky like using Automation to open another session of Access, are you? -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message news:44435147-8EF2-4B65-8EC6-B7BE967E55EF[ at ]microsoft.com... [Quoted Text] > Access does not show on the taskbar, only under Task Manager. Also, I > usually > close an open database before exiting Access and some of my databases do > not > include any code at all. I'll read the reference. > > "Chris Mills" wrote: > >> I presume you mean "stays on the taskbar". >> >> Various programming "bugs" (actually I think they are Access bugs) can >> cause >> this, and they can be a right pig to find. >> >> See: >> http://www.mvps.org/access/bugs/bugs0005.htm >> >> Also (I don't see it listed there) I'm under an impression that: >> If Something Then >> ....instead of... >> If Something = True Then >> ....can cause this bug. Or some bug. >> (well, I'm thinking back to A97 whatever) >> >> Chris >> >> "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message >> news:A723CE8A-6747-4BDC-9739-A58606A3576E[ at ]microsoft.com... >> > Occasionally, the MSACCESS.EXE process does not stop after I exit >> > Access. >> The >> > process shows about 50% CPU usage in Windows Task Manager. Sometimes >> > memory >> > usage increases slowly but not always. As far as I can tell, there is >> nothing >> > going on before I exit. >> >> >>

Re: MSACCESS.EXE does not stop after exiting Access 2003 mcglincym 01.09.2006 17:31:02 I am checking for any objects not closed and set to nothing as suggested in the link posted by Chris Mills. I use one database as a library and reference it from other databases with forms. My library procedures use a browse dialog from the Office Object library, statistical functions from the Excel Object library, and a declared HTMLHelp function from HHCtrl.ocx. I think that I no longer use Automation of Access but I'll check. "Douglas J. Steele" wrote: [Quoted Text] > You're not doing anything funky like using Automation to open another > session of Access, are you? > > -- > Doug Steele, Microsoft Access MVP > http://I.Am/DougSteele > (no private e-mails, please) > > > "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message > news:44435147-8EF2-4B65-8EC6-B7BE967E55EF[ at ]microsoft.com... > > Access does not show on the taskbar, only under Task Manager. Also, I > > usually > > close an open database before exiting Access and some of my databases do > > not > > include any code at all. I'll read the reference. > > > > "Chris Mills" wrote: > > > >> I presume you mean "stays on the taskbar". > >> > >> Various programming "bugs" (actually I think they are Access bugs) can > >> cause > >> this, and they can be a right pig to find. > >> > >> See: > >> http://www.mvps.org/access/bugs/bugs0005.htm > >> > >> Also (I don't see it listed there) I'm under an impression that: > >> If Something Then > >> ....instead of... > >> If Something = True Then > >> ....can cause this bug. Or some bug. > >> (well, I'm thinking back to A97 whatever) > >> > >> Chris > >> > >> "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message > >> news:A723CE8A-6747-4BDC-9739-A58606A3576E[ at ]microsoft.com... > >> > Occasionally, the MSACCESS.EXE process does not stop after I exit > >> > Access. > >> The > >> > process shows about 50% CPU usage in Windows Task Manager. Sometimes > >> > memory > >> > usage increases slowly but not always. As far as I can tell, there is > >> nothing > >> > going on before I exit. > >> > >> > >> > > >

Re: MSACCESS.EXE does not stop after exiting Access 2003 Gordon Clark 28.09.2006 12:39:02 I'm running into the same issue - haven't heard from any users if this is happening to them, as of yet. What happens is after the screensaver mode kicks in and I'm logged off the machine (XP relogon to network/machine), I'll key in my password, opening to Desktop, and the VBA project window will be open - stating "No open projects" on the title bar. I've seen as many as four instances of MSACCESS.exe running concurrently in Taskman on these occurences. The VBA window does occupy the taskbar normally, with the application name in the titlebar. Close that, open Taskman, and still find the four instances running 'behind the scenes'. What I haven't done = to check for instances running where I may not see the VBA window.... On DAO - not really using that - there is perhaps use of at least one RecordsetClone, but that usage is buried deep in the code of an infrequently used form. Your mention of implicit "If Something = True Then..." is definitely something I can check for, I do like to save a keystroke where possible *eek*. Platform is XP Pro, Access 2002, native 2002 version DB. Thank you for your previous inputs - looks like I've got some homework to do.... =(. Gordon "Chris Mills" wrote: [Quoted Text] > I presume you mean "stays on the taskbar". > > Various programming "bugs" (actually I think they are Access bugs) can cause > this, and they can be a right pig to find. > > See: > http://www.mvps.org/access/bugs/bugs0005.htm > > Also (I don't see it listed there) I'm under an impression that: > If Something Then > ....instead of... > If Something = True Then > ....can cause this bug. Or some bug. > (well, I'm thinking back to A97 whatever) > > Chris > > "mcglincym" <mcglincym[ at ]discussions.microsoft.com> wrote in message > news:A723CE8A-6747-4BDC-9739-A58606A3576E[ at ]microsoft.com... > > Occasionally, the MSACCESS.EXE process does not stop after I exit Access. > The > > process shows about 50% CPU usage in Windows Task Manager. Sometimes memory > > usage increases slowly but not always. As far as I can tell, there is > nothing > > going on before I exit. > > >