Access instance remains in memory once closed (4 Viewers)

[isladogs]

Thanks Ron. That's good news!

Please could you provide the version / build for each. I tested in both:

• Windows 11 Pro 25H2 26200.7705 and Access 365 v2603 19727.20000 Beta Channel
• Windows 10 Pro 22H2 19045.6809 and Access 365 v2603 19728.20004 Beta Channel

 

[RonPaii]

Thanks Ron. That's good news!

Please could you provide the version / build for each. I tested in both:

• Windows 11 Pro 25H2 26200.7705 and Access 365 v2603 19727.20000 Beta Channel
• Windows 10 Pro 22H2 19045.6809 and Access 365 v2603 19728.20004 Beta Channel

Windows 11 Pro, Version 25H2 (OS Build 262000.7623)
Microsoft® Access® for Microsoft 365 MSO (Version 2511 Build 16.0.19426.20260) 64-bit Monthly Enterprise Channel

In an unrelated note. I do on occasion get the following pop-up error on reboot/shutdown. All programs are closed before the shutdown.

Access application error: The instruction at 0x00007FF6B6144735 referenced memory at 0x0000000000000048. The memory could not be read.

 

[isladogs]

Thanks

 

[RonPaii]

Thanks

I just tried it on Runtime. The 1st form opened but Access hung on opening the 2nd db. Ended with a runtime error.

Event viewer showed no error or warning, but this information log.

- System

  - Provider
   [ Name]  Microsoft Office 16 Alerts
  - EventID 300
   [ Qualifiers]  0
   Version 0
   Level 4
   Task 0
   Opcode 0
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2026-02-06T14:02:57.1312249Z
   EventRecordID 12
   Correlation
  - Execution
   [ ProcessID]  0
   [ ThreadID]  0
   Channel OAlerts
   Computer PC0075.pa.packairinc.com
   Security

- EventData
   Microsoft Access Execution of this application has stopped due to a run-time error. 
   The application can't continue and will be shut down. 
   507898 
   16.0.19628.20150

Don't know an easy method to get the version but registry is as follows
RuntimeVersion v2.0.50727
Windows 10Pro Version 22H2 (OS Build 19045.6456)

Maybe add to the 1st form the current Windows/Access information to report back to you.

 

[isladogs]

Yes. I'd expect it to fail using / simulating Runtime.
In fact, no need to try and do the automation as you will get that error if you just click the View / Edit Code button when using Runtime

In case you or anyone else would find it useful, I do have a free Windows / Office / Access version checker add-in:

Access/Windows Version Check Add-In

Use this add-in to obtain the full Access/Windows/Office 365 version and bitness information. It also provides details of the VBA references used by the host application

www.isladogs.co.uk

However of course you can't load add-ins in Runtime mode but you run run an add-in such as that as a standalone app in Runtime mode.
I haven't got a current VM with an actual Runtime version available to test on.

 

[RonPaii]

Yes. I'd expect it to fail using / simulating Runtime.
In fact, no need to try and do the automation as you will get that error if you just click the View / Edit Code button when using Runtime

In case you or anyone else would find it useful, I do have a free Windows / Office / Access version checker add-in:

Access/Windows Version Check Add-In

Use this add-in to obtain the full Access/Windows/Office 365 version and bitness information. It also provides details of the VBA references used by the host application

www.isladogs.co.uk

However of course you can't load add-ins in Runtime mode but you run run an add-in such as that as a standalone app in Runtime mode.
I haven't got a current VM with an actual Runtime version available to test on.

This was a real Runtime computer.
It crashed clicking the next form button.

 

[isladogs]

Not sure what you mean as it only has one form.
Again it would have been surprising if it had worked in runtime.
To get all the version info, the code runs various WMI functions, checks multiple registry locations, runs various SysCmd checks and even does a web scrape of the Office 365 release history web page to get the Office YYMM version number.

 

[RonPaii]

Not sure what you mean as it only has one form.
Again it would have been surprising if it had worked in runtime.
To get all the version info, the code runs various WMI functions, checks multiple registry locations, runs various SysCmd checks and even does a web scrape of the Office 365 release history web page to get the Office YYMM version number.

I added a registry lookup to display the Access version and error trapping to catch the error. Apparently Access automation from runtime is not allowed.

 

[cheekybuddha]

Apparently Access automation from runtime is not allowed.

Colin did try and explain that to you in Post #85

I'd expect it to fail using / simulating Runtime.
In fact, no need to try and do the automation as you will get that error if you just click the View / Edit Code button when using Runtime