Software Deployment Question

Is there any way to stop the Access Runtime from killing the calling process?

11/05/2015 1115 views
Using the method described here (http://www.itninja.com/software/microsoft/access-runtime/2013-14), the access 2013 runtime kills the calling process when I attempt to run it from another process, in this case an InstallShield installer. I assume its because it "thinks" it is within its own bootstrapper. Is there possible an option for the config.xml that would prevent this from happening?
1 Comment   [ + ] Show comment


  • not so much in the cofig.xml but more than likely you need to set an installshield equivalent of start /wait. Some more clues on your installer would help

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ