Forum Discussion
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.
4 Replies
- HeinziATIron Contributor
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 SubWorks 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?
Hi,
Are you sure that the full version and the runtime are at the exact same build? I ask because there are a lot of changes going on, e.g. related to the new zooming functionality and to recent bug fixes.
Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK- RM-DTOccasional Reader
Servus Karl,
I checked once again ... but both versions are equal.
I try to downgrade to a known proper version ... but it ist not possible with this number in the xml.
Danke und Servus,
Robert- HeinziATIron Contributor
You can find a list of Current Channel version numbers here:
You can also use OfficeC2RClient.exe instead of ODT/XML, which is, in my opinion, a bit easier. It's described as "Method 1" here: