Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Wed Jan 5 17:18:48 CST 2011
<<< The Access 2007 application in question does not use any automation or third-party controls. >>> OK. What about Win32 API? <<< However, it does contain a fair amount of VBA code, so I am going to go hunting for possible missing "Clean up" instructions. >>> Yes. First of all look for cross-referenced object instances. Also, kill all "hanging" MS Access instances, try to start your MS Access application, run it for some time and check is there just one MS Access instance running or more than one?.... Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: 6 ?????? 2011 ?. 1:53 To: Access Developers discussion and problem solving Subject: Re: [AccessD] MSACCESS.EXE Still Visible in Windows TaskManagerafterDoCmd.Quit Command Shamil, The Access 2007 application in question does not use any automation or third-party controls. However, it does contain a fair amount of VBA code, so I am going to go hunting for possible missing "Clean up" instructions. Thanks for your help. Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: Wednesday, January 05, 2011 3:53 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] MSACCESS.EXE Still Visible in Windows Task ManagerafterDoCmd.Quit Command Hi Brad -- Do you use Automation, any kind of advanced VBA coding or third-party controls in your MS Access 2007 application, .... anything "non-standard"? :) Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: 5 ?????? 2011 ?. 23:11 To: Access Developers discussion and problem solving Subject: [AccessD] MSACCESS.EXE Still Visible in Windows Task Manager afterDoCmd.Quit Command Occasionally, we notice that an Access 2007 application is still visible in the Windows Task Manager after the "DoCmd.Quit acQuitSaveNone" is issued. (Even after waiting 10 minutes after the DoCmd.Quit command is issued) To the user, the Access application has disappeared, but it still is visible in the Windows Task Manager under the Processes Tab We can, of course, kill off the application in the Windows Task Manager, but we would prefer to not do this. I am curious as to why this is happening. Is there something that can be done in the Access application to prevent this? Have other people seen this happen? Thanks, Brad -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com