Is there any way to stop the Access Runtime from killing the calling process?
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?
There are no answers at this time