Access hangs for at least 30 seconds when switching tabs if the Property sheet is open

[Tenmakk]

Does anyone know why this is happening how how I can fix it? The busy circle icon appears during this time. The only way for me to avoid this is to close the properties sheet each time I switch tabs. It's very inconvenient, especially when I forget to. This is slowing my progress to a crawl.

[aytee111]

Do you have a timer event running in the background?

[John_G]

Try closing all other running applications, especially web browsers. I have seen these take up a LOT of CPU time, depending on the website.

[Tenmakk]

Do you have a timer event running in the background?

Yes, I do have a timer that can be set to start from 30 to 900 seconds. And I set the countdown text box to: Me.txtTimeLeft.SetFocus.

This is what I have:

Private Sub Form_Timer()
    timer = timer - 1 'countdown
    If timer > -1 Then Me.txtTimeLeft.Value = timer 'show the time in the textbox
    If timer = 0 Then
        '......put event here
        TimerInterval = 0 'stop the timer
        DoCmd.Beep
        MsgBox "time is up"
    End If
End Sub

Thanks.

[aytee111]

That is what is causing your problem.

[Tenmakk]

Can anyone answer how I can fix this? That's obviously why I'm here. Please don't give attitude, I don't have much experience with Access and what I can't do, I am asking for help. I know how negative people on message boards can be and would prefer no response to a sarcastic one. Please keep it positive.

Thank you.

[aytee111]

You have a choice - either put up with it or switch the timer off. That is not negative, it is the way it is.

[Tenmakk]

There you go. Thank you for suggesting a way to deal with it, rather than just telling me my problem. I never said you were negative. But your post was unhelpful and perhaps a bit sarcastic.

[Tenmakk]

Thought I would give an FYI to anyone having the same issue. This isn't the solution. Timer is NOT the problem. I'm still getting a prolonged busy wheel. Thank you for the tip about closing applications but that didn't fix it either. I'll go to a different forum for this one because I'm sure someone knows a solution for this.

[CJ_London]

has your db been under development for a long time or had a lot of changes to the code? If it has, it is likely there is a lot of junk floating around in the background which may be causing the problem. Suggest you decompile - see this link http://www.fmsinc.com/microsoftacces.../decompile.asp and then compact and repair

[Tenmakk]

Ah. It seems that John_G and you were right. I just had to restart my computer. Thank you both for helping.