Hey Folks,
I am getting a 'The command or action 'Quit' isn't available now' error when attempting to quitacess via macro or code. At times the quit function will work then as soon as it displays the error above, with absolutely no difference between working or error state at all, it will not work again unless I move the quitaccess macro around and then back to where it needs to be again - as if something needs to be reset or closed for this action to work once it fails the first time. I am pretty confident (90%) that it isn't the logic in the code, it isn't a seurity or trust issue, and it isn't a read-only issue as I tried to rule out all those options. Is there a brute force method that can just quitaccess when it's called via macro or code so that access doesn't render the above error and remain opened after the other macros finish? It appears that a lot of folks have this issue and no one seems to have any solutions (I looked online for hours in vain). If someone can help or suggest something or know a way around this problem, I would greatly appreciate it!! I just don't get it ... might be Access 2010/2007 issue?? Thank you!
I am getting a 'The command or action 'Quit' isn't available now' error when attempting to quitacess via macro or code. At times the quit function will work then as soon as it displays the error above, with absolutely no difference between working or error state at all, it will not work again unless I move the quitaccess macro around and then back to where it needs to be again - as if something needs to be reset or closed for this action to work once it fails the first time. I am pretty confident (90%) that it isn't the logic in the code, it isn't a seurity or trust issue, and it isn't a read-only issue as I tried to rule out all those options. Is there a brute force method that can just quitaccess when it's called via macro or code so that access doesn't render the above error and remain opened after the other macros finish? It appears that a lot of folks have this issue and no one seems to have any solutions (I looked online for hours in vain). If someone can help or suggest something or know a way around this problem, I would greatly appreciate it!! I just don't get it ... might be Access 2010/2007 issue?? Thank you!
