Tweet
Hi, I found that when running Msaccess application from an autoplay studio exe that it will run and open the msaccess application but, Msoutlook does not talk (respond to commands) from MSaccess properly anymore. The reason was that the compiled autoplay exe was set at "highest available" (under the advanced tab). If its set at "invoker" there are no problems. I would have thought that the "highest available" setting in autoplay would mean it defaulted back to "invoker" if it needed to. Anyhow the point I make is that its a trap that gives no warning of failure when an autoplay exe runs a windows software. Windows (it appears) thinks that privileges the autoplay exe is using arent correct (or something) and so the application you try to run doesnt talk/work properly 100%. (key words for search engines.. Automation object, Set OutApp = CreateObject("Outlook.Application", "localhost") activex can't create object 429.