Blinking Macros

[Mike]

,
I've Setwarnings off, but:

Does anyone know how to suppress a macro from blinking while performing open/close on forms/reports/tables/queries etcfrom the switchboard formHi , thereby creating the illusion that my macro is an efficient and elegant piece of work, rather than the long-winded pile of trash it unquestionably is?

Ideally, an "operation in progress" type of message or hourglass pointer would be good, but if this isn't possible, just stopping the blinking blinking alone would be good.

Thanks in advance,
Mike

 

[Ken Snell]

See Echo action... it turns screen updating/painting on and off.

Also see Hourglass action.

--

Ken Snell
<MS ACCESS MVP>

,
I've Setwarnings off, but:

Does anyone know how to suppress a macro from blinking while performing

open/close on forms/reports/tables/queries etcfrom the switchboard formHi ,
thereby creating the illusion that my macro is an efficient and elegant
piece of work, rather than the long-winded pile of trash it unquestionably
is?

Ideally, an "operation in progress" type of message or hourglass pointer

would be good, but if this isn't possible, just stopping the blinking
blinking alone would be good.

 

[Mike]

Thanks for the reply Ken,

It's still doing a bit of blinking, but better than before. Is there an easy way to keep my maximised main form in the foreground to mask the macro (now successfully hourglassed) working away behind it?

Thanks again,
Mike

 

[Ken Snell]

Without knowing more about what it's doing, I can only suggest that you
should change all the OpenForms to state that the Window Mode should be
Hidden and not Normal.
--

Ken Snell
<MS ACCESS MVP>

Thanks for the reply Ken,

It's still doing a bit of blinking, but better than before. Is there an

easy way to keep my maximised main form in the foreground to mask the macro
(now successfully hourglassed) working away behind it?

 

[Mike]

Thanks for sticking with me Ken,

The user would normally call the macro from a form button. The macro opens several tables (therefore I don't have a hide option) in edit-mode, purges them, and repopulates them with imported data. Whenever I use the macro it flashes as each table is opened as if the display is maximising the table (but doesn't display the data), closes it, and does the next one. Interestingly, using the echo command seems to slow the macro down so it doesn't blink as quickly, but still doesn't look as slick as if it didn't blink at all...

Hope this helps,
Mike

 

[Steve Schapel]

Mike,

PMFJI. It seems to me that there are very likely simpler and smoother
ways of achieving your purpose. To be honest, I can't imagine a
scenario where it would be necessary or advisable to use a macro to open
a table datasheet. On the face of the information you have given so
far, a Delete Query and an Append Query could do the job, via OpenQuery
actions in your macro if you like.

 

[Ken Snell]

I'm with Steve Schapel on this one. If you want to further tidy up the
"flashing", then you'll need to change what the macro does... in short,
don't open tables, use delete queries to remove data from tables. Etc. Other
than that, I don't have other tricks to suggest!

--

Ken Snell
<MS ACCESS MVP>

Thanks for sticking with me Ken,

The user would normally call the macro from a form button. The macro opens

several tables (therefore I don't have a hide option) in edit-mode, purges
them, and repopulates them with imported data. Whenever I use the macro it
flashes as each table is opened as if the display is maximising the table
(but doesn't display the data), closes it, and does the next one.
Interestingly, using the echo command seems to slow the macro down so it
doesn't blink as quickly, but still doesn't look as slick as if it didn't
blink at all...

 

[Steve Schapel]

Mike,

Could you please give full details, with all Actions and Arguments, of
some of the macros that are causing this problem? Thanks.