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

Comments

  • 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
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity