×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Immediate window stops updating on continuous run

Immediate window stops updating on continuous run

Immediate window stops updating on continuous run

(OP)
I have lengthy code that I have DEBUG.PRINT scattered within so I can watch the code process. I am currently getting the Immediate window will be populated with a few rows (not always the same rows) but no more populating to the immediate window. After a random time period, the Immediate window populates with all the rows. Nothing is "missing" from the immediate window, it appears the window is caching all vs printing right away.

Is there a known issue for immediate window not always displaying right away? Is there a caching feature in play that I am not aware of?

Side note: I eventually hope to use the immediate window (output) in a window for end users to see the app is working vs looking like it's locked up or frozen.

RE: Immediate window stops updating on continuous run

Instead of Debug.Print, why not use a simple label on your Form and display what's going on to the user. You can do something like:

...
lblMsg.Caption = "Getting your coffee..."
lblMsg.Refresh
...
lblMsg.Caption = "Getting donuts now..."
lblMsg.Refresh
...
 


---- Andy

There is a great need for a sarcasm font.

RE: Immediate window stops updating on continuous run

(OP)
Okay, but until I do make visible to end users, I am perplexed why the Immediate window doesn't show all rows of debug.print as they are happening vs caching then dumping a bunch at a time or wait until done processing to display.

RE: Immediate window stops updating on continuous run

Refreshing and the number of lines displayed by Debug.Print may be just limited.

I just tried this in Excel VBA:

Dim i As Integer

For i = 1 To 500
    Debug.Print "This is " & i
Next i
 
And I've got lines:
This is 302
This is 303
This is 304
This is 305
...
This is 498
This is 499
This is 500
 
So first 301 lines were over-written and not displayed at all.


---- Andy

There is a great need for a sarcasm font.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close