StopMacro for a failed command?

[Guest]

I have a Macro to be run through clicking the Command Button: openQuery.
The TableQuery is to download the data from an ODBC-table in my remote
office Mainframe computer. At times the link is broken due to the connection
or whatever reasons, in other words the query is not successful run due to
the "call failed".
If the TblQry is not in the Macro, I just close the error message "pop-up
window". Since I put it in the Macro, after closing the "call failed"
window, the DB is still busy with the Hourglass, I have to use the "Task
Manager" to close Access completely.

How do I make this process stop if the "OpenQuery" doesn't work out due to
the "call failed" instead of using the "Task Manager" to close Access (that
DataBase) completely ? In other words, if the OpenQuery doesn't work, how do
I proceed to the next action: StopMacro ?

Herebelow is my setting of that Macro:

Hourglass (to set this in order for the user to know its busy, because it
may take
some time to download the file)
SetWarnings (No)
OpenQuery (this query need to submit userID and password to link into the
ODBC-
tables in our Main Office Mainframe)
StopMacro

I appreciate for any help/suggestion ?
thanks
Karen

 

[Allen Browne]

Instead of using RunSQL or OpenQuery to run this action query in a macro,
use the Execute method in code. The code then hears about the error, and
skips out of the rest of the routine.

Example in :
Action queries: suppressing dialogs, while knowing results
at:
http://allenbrowne.com/ser-60.html