Forum Discussion

RM-DT's avatar
RM-DT
Copper Contributor
Sep 03, 2026

Inconsistent behaviour of AccessRuntime and Access (Developer Version) - Office 365

I am using Access Version 2608 (Build 20326.20132) and I am having big problems because of a differnt behaviour of Runtime and Full (same version).

When setting a short timer (for initialisation / 10ms) within the Form_Load event, the timer starts in the "Full-Version" of Access365  immediatly after finishing the Form_Load event (not further action in the other events). 

The Runtime-Versions don't accept the Timer-Value I set befor in the Form_Load event.

Remark: With an old version (I don't know which one, because all customer PC were updated) it works perfekt, also with AccessRuntime. A very old customer installation (16.0.18827.20164) works perfekt.

What can I do, because the application is broken down at many customer sites ... and I have to solve this problem very urgent.

developer
office 365

8 Replies

  • RM-DT's avatar
    RM-DT
    Copper Contributor
    Sep 06, 2026

    Hi to all,

    I was able to locate the reason for the timer-fail in my application !!! The problem occurs in the Full- and Runtime-Version. 

    It is very crazy, because in my form_open procedure, I change the style of my TabControl-Element in the form, using the command "Me.ksz_register.Style = 2". This command ist responsible for the malfunction. After setting this command to a comment, the program works fine again. I disabled the Tab-View in development mode (properties). This is at the moment ok for me, but not very useful if some changes have to be done in not visible tabs.

    Servus,

    Robert

  • HeinziAT's avatar
    HeinziAT
    Iron Contributor
    Sep 04, 2026

    Another question: If the timer hangs, can you "unblock" it by moving the Access window or switching between the form tabs? If yes, your problem might have the same root cause as a known Timer issue.

    • Karl_Donaubauer's avatar
      Karl_Donaubauer
      MVP
      Sep 04, 2026

      Hi Heinzi,

      If Robert were finally a second important Microsoft customer 😉 affected by your personal timer bug, I'd follow up with the Access Team again to get them to raise the fix priority. 

      BTW, is it some weird cultural/economic hegemony thing that the three of us aren’t discussing this in Austrian dialect or at least in German? 🤔

      Servus
      Karl
      ****************
      Access Forever News DevCon
      Access-Entwickler-Konferenz AEK 10./11.10. Nürnberg

      • HeinziAT's avatar
        HeinziAT
        Iron Contributor
        Sep 07, 2026

        Yes, the irony of the three of us conversing in English has not been lost on me. :-) But, you know the saying: The official language of international business is "bad English".

        Our visibility workaround for the timer bug works well so far. So, as long as we are the only ones affected, "low priority" is perfectly fine for me.

  • HeinziAT's avatar
    HeinziAT
    Iron Contributor
    Sep 03, 2026

    Cannot reproduce. This is what I tried: Simple form with one label (Bezeichnungsfeld0) initialized to "Waiting..." and the following events:

    Private Sub Form_Load()
    Me.TimerInterval = 1
End Sub

Private Sub Form_Timer()
    Me.Bezeichnungsfeld0.Caption = "Done: " & SysCmd(acSysCmdGetFullVersion)
    Me.TimerInterval = 0
End Sub

    Works fine in 20326.20132 (a) full Office, (b) full Office with /runtime switch, and (c) AccessRuntime installed only.

    Do you have a minimal example that reliably reproduces the issue?