ispaydeu Posted December 16, 2006 Report Share Posted December 16, 2006 Ok, so it took me many hours to figure this out and I have been scrathcing my head for weeks. So, I had a really comples macro that was running and was calling lots of different macros through out it. One part in particular is setup so that the macro calls up access to run. Then, within Access I have an autoexec macro that runs and processes a file on my computer and sends out the results. Here is the problem... Sometimes when the autoexec program runs, one of the queries returns a null error. Now I am VERY experienced with Access and know how to fix the error within the query. However, here is the problem. If I use any command in ME to activate the Access program that has the Autoexec in it, ME will NOT move on to the next step of the macro (hit enter, compare controls, compare pixel, ANYTHING) until the Access autoexec macro has completed. So, as the MOST basic example in the world. If I setup a macro, and the only line in it is to call up my access database, ME will not complete until the Autoexec macro within Access is complete. Which creates a problem, I can't tell my macro to hit ENTER or anything on that Null prompt because it is still on the previous launch command. So, if my macro is... Program Launch: "Access database that has an autoexec macro inside of it" Program Launch: "notepad.exe" It will NEVER launch the notepad.exe or do ANYTHING at all until the access's autoexec is done. So I can't hit enter on errors. Or do anything. Now, If I open an access database that does not have an autoexec inside of it, and just plain out open it, the next command is almost instantaneous. Also, when the prompt comes up about the null error, and my PC is not doing a darn lick of a thing, not thinking, nothing, it still will not move on until the macro within access is complete, so my macro just gets stuck if an error ever comes up. Also, I already have all the "do not display error" messages in Access turned off, but apparently you can't turn off the Null message. Has ANYONE ever experienced this? Did you find a work around? What do you recommend? Anyone have any ideas why this is occuring (maybe macros within access use similar features to macro express and they cannot coeixit so one waits for the other to complete?) Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.