Macro From Button Freezes Access

[Guest]

I have created a macro that runs an append query. It runs through macros
windows fine. When I running the macro from the button on a form, Access
freezes. Some patch or fix out there??

 

[Ken Snell [MVP]]

More than likely there is a problem with the macro. Please give us details
about the query and the macro.

 

[Guest]

The query prompts for account number, finds that account number in Oracle
table and appends local database table with data (names, address, etc.)

The macro opens that query and closes that query.

The query works fine, and the macro works JUST FINE when run alone. Access
only freezes if I run it by clicking the button.

 

[Ken Snell [MVP]]

How is the macro tied to the button? Via the Click event? Describe how you
assigned the macro to the event.

 

[Guest]

YES. The macro is assigned via the click event.

 

[Ken Snell [MVP]]

If the macro runs correctly on its own, then clicking a button to run it
would not be expected to be a problem. When you say ACCESS "freezes", how do
you determine that? Is anything going on at all? Is the macro turning off
SetWarnings before it runs the query? Is it possible that the query is
actually finishing its work? What do you see as a result when you run the
query / macro by itself, versus the result when you click the button on a
form?

I am thinking that there is more to this issue than what you've posted so
far.
--

Ken Snell
<MS ACCESS MVP>

 

[Guest]

The macro must be finished; it should only take a few seconds - appending a
table.

When I mean "freezes," Access doesn't crash, but it won't respond to any
sort of click - on form fields, scroll bars, menus, etc.

You are right about having a little more going on: I had "ECHO" set to off
in the macro - (so the queries aren't visible when they run??) . I removed
that first line in the query and TA DA, it worked. Even if I SetWarnings to
Off it works.

THANK YOU for helping!!!!

 

[Ken Snell [MVP]]

Append queries do not "show" on the screen when they run, so you shouldn't
need the ECHO action in the macro at all.

Glad it's working now.

--

Ken Snell
<MS ACCESS MVP>