Application.Echo quit working. Any suggestions?

Question

I purchased MSAccess 2013 Pro in December, and Application.Echo worked as it (and Docmd.Echo) has always worked since I began using Access about 1997.  I typically set up a debugging macro to turn the echo back on, when needed.

But recently Application.Echo (and Debug.Echo) simply quit working, and my application looks and behaves unprofessionally.

I tried using SomeForm.Painting = False; but that only works for a single form, and is virtually useless in my multiform, multi-tab application.

I can only assume that a bug was introduced into Access during one of the automatic updates that causes Application.Echo to become useless.

Any suggestions?

Dan

Answer 1

Tom, thanks for your reply.

I found the problem, and it is a serious one, at least for me.  After updating from Access 2002 to 2013, I was disappointed with the lackluster appearance of the main form border that 2013 presented.  I experimented and found that if I changed the main form to a "popup", the application border would look good again.  

Now I realize that Application.Echo is limited to simple forms (no popups or modals.)  Looking back over my 18 years of Access development, I don't recall using a popup or modal form in the past.  There was no need.  Therefore, Docmd.Echo (and Application.Echo) worked fine.

I have tried SendMessage(hwd, WM_SETREDRAW, 0&, 0&), and LockWindowUpdate (hwd). But unless I am missing something, they lock only one window at a time, and are virtually useless for a multi-subform application; that is a main form with multiple subforms simultaneously updating.

If anyone knows a good API that will lock the entire application, I would appreciate that knowledge.  Or, if anyone knows how to replace the unimpressive default border without using a popup, that would be equally appreciated.

Dan

Answer 2

Create a new form and put in the below code. This is what I used for testing. You cannot move the form for 5 seconds, then it works again. How does this play out on your machine?

Private Sub Form_Open(Cancel As Integer)

    Me.TimerInterval = 1000

End Sub

Private Sub Form_Timer()

    Static tickcount As Integer

    tickcount = tickcount + 1

    Application.Echo False

    If tickcount > 5 Then

        Application.Echo True

        Me.TimerInterval = 0

    End If

    Debug.Print Time$, tickcount, TimerInterval

End Sub

Answer 3

Tom,

Thank you so much.  For the first time since purchasing the Access 2013 Pro in December 2014 I was able to activate the product; that is, until now it never installed completely.  It would give an error before 90% installed.  Maybe now I can work offline as I intended to do from the beginning.

Unfortunately, Application.Echo still does not work. It will not freeze screen repainting, as designed.  Nor will Docmd.Echo (the older naming convention) freeze repainting.  

I am at a loss. I have been working on this major application for 1.5 years--until December in Access 2002, and then in Access 2013. No problems with Application.Echo until recently.  Now all my work is for naught if I cannot solve this screen painting functionality issue.

Help!

Dan

Answer 4

I have to tell you sometimes years go by that I don't use the Echo method. How are you using it, what are you expecting, and what are you not seeing?

It seems to work fine for me freezing the screen until Echo is set back to True.  Maybe time to repair your Office installation.

Thanks for your reply,

I use Echo to freeze the screen during data updates which helps prevent flicker and an overall cheap, sloppy appearance.

I attempted to perform a quick repair of Access 2013 Professional.  As expected (seriously, "As Expected!") it popped up a useless "Working On It" screen, and proceeded  to go into a perpetual loop. I had to use Task Manager to stop the loop.

I just started the full, online repair, that gives the same, worrisome, "Working On It" message; but at least this one has an extra message, "Step 1 of 4", which is somewhat comforting.

I will let you know how things work out.

Dan

.

Answer 5

I have to tell you sometimes years go by that I don't use the Echo method. How are you using it, what are you expecting, and what are you not seeing?

It seems to work fine for me freezing the screen until Echo is set back to True.

Maybe time to repair your Office installation.