By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,241 Members | 2,192 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,241 IT Pros & Developers. It's quick & easy.

Fried brain by 10am - wierd "fake" hang problem

P: n/a
Hi all,

I'm running some seemingly lovely code that works fine in the end, i've
added in some syscmd meter lines to dsiplay a nice status message as
the code progresses but they just stop updating.

In fact if i stay in Access and let the code run (it takes some time as
it is loading and processing very large text files) it looks fine but
if i alt-tab away and then come back it appears to have died, although
if i ctrl-break and restart the code execution it seems to have been
going on anyway.

Driving me nuts - any ideas?

Thanks,

Rob.

Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Once you leave the access window when code is running, then the window
stops updating - if you put a DoEvents after each status message update
however this should force the screen to update before going to the next
command.

Nov 13 '05 #2

P: n/a
Fabulous... why on earth is that needed then? It works a treat but i
can't see why it should be needed at all.

Rob.

Nov 13 '05 #3

P: n/a
DoEvents allows designers to force the code to stop and examine the
events and triggers that have happened since the code started
running... otherwise the code carries on churning and ignores the
interface.

Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.