Access 2016 Processes not being killed during Automation but same works for Access 2013/10/07 -


we have access automation software opening instance of ms access 2016 using com , fetching data of tables/reports etc access database. once done, close ms access database -

  1. calling database.close()
  2. assigning null value referenced variables
  3. calling closecurrentdatabase() of access application object
  4. finally calling quit() method of access application object
  5. assigning null value access application referenced variables
  6. calling gc.collect() & gc.waitforpendingfinalizers() in separate thread.

doing of above kills ms access 2013 instances fails ms access 2016. processes linger on time , keep consuming ~50 mb ram , ~10% cpu though our automation completed , our code has quit. find these processes killed time later.

this lingering on of processes causing high cpu / ram usage issues find more 50 instances open.

is there known issue in ms access 2016 while closing or connect post activity (like connect server , send data) when application.quit called.

would appreciate advice in regards.


Comments

Popular posts from this blog

Command prompt result in label. Python 2.7 -

javascript - How do I use URL parameters to change link href on page? -

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -