Owl wrote:

Thank you for your reply, Dirk.

The actions in my Quit macro (which works - to exit the database - on
every single other database I use OUT of Runtime) are simply Quit (and of
the options to Save or Prompt or Exit, I have selected Exit).

By not working, I mean it comes up with the following error message (THEN
paradoxically carries out the action requested):

You can’t carry out this action at the present time.
You tried to run a macro or used the DoCmd object in Visual Basic to carry
out an action. However, is performing another activity that prevents
this action from being carried out now.
For example, no actions on a form can be carried out while is repainting
a control or calculating an expression.
Carry out the action later.
Then there is an OK button and when I press the OK button, I am taken out
of the database as I wanted to be immediately with no further problem, but
I don't want the error message coming up.


The macro is invoked from a switchboard.

So far, I am using my database with Runtime on a computer WITH Access
2007, but am hoping to be able to try it out on a computer without Access
tonight -
hopefully I will have the Quit problem sorted out by then. I have Runtime
and my small simple application database file (not split - I am going to
try to do it with a copy of the database split when I have mastered this
unsplit one) in the same folder.

I have made the folder that they are in, a Trusted Location.

Does the Quit macro (when not using the runtime) close Access entirely or
just the file currently opened? The runtime cannot be used without a file
opened so the latter would not be allowed.