Access don’t respond in a click at a form(button)

Gert Hansen

New member
Local time
Today, 12:44
Joined
Nov 28, 2024
Messages
4
Hi all
I’m a new member of the group.
I’m running Windows 11 using Parallels Desktop on a new Mac. Previous the same with Windows 10 on another Mac.
All my applications can perform in another windows 11 windows PC.
Microsoft 365 applications (including Access) have been downloaded.
AND NOW TO MY PROBLEM:

Mouse clicks in tabels, queries etc. are working.
But when I use the mouse in a form the result is always:
The expression On Click you entered as the event property setting produced the following error.
A problem occurred while ## An Access application name here ## was communicating with the OLE server or ActiveX Control.


Can’t close the form (any form). Only close Access.
Can someone help me?
Gert
 
Not much to go on and I have no experience of ms access run on a Mac. But that can happen if your vba is missing a relevant library - check to see if you have any missing libraries
 
Hi. Welcome to AWF!

The first thing you could try is perform a Compact and Repair to see if it resolves the issue.

File > Info > Compact & Repair Database
 
This error is a well known error (for us who use non-English version of Access) and has been discussed here several times.
See the following thread by @MajP and the solution offered by @sonic8

 
Not much to go on and I have no experience of ms access run on a Mac. But that can happen if your vba is missing a relevant library - check to see if you have any missing libraries
There are no missing libraries.
 
In that case suggest check out the link in post#4
 
There are no missing libraries.
The problem is probably not related to somerhing in a given access-application.
I’ve created a completely new access database. Created a single table. Created a button on the form, which purpose is to open the table.
When the form is opened and I press the button, then the errormessage is shown.
I can close in upper right corner of the form or close access.
Consequently the problem must be some kind of setting that is wrong or missing.
 
I’ve discovered that the real problem was, that my new Mac computer had a M3-processor.
The same problem was in the first period after the M2-processor came. Microsoft came later with an update, which solved the problem.
The corresponding update to the M3-processor has not yet been launched.
I solved my problem by bying a new Mac with a M2-processor. And all was ok.
 
you couldn't pay me to use a Mac
That statement is all that's needed to apply wonderfully to me :)

For the plethora of Windows/Android vs. Apple writings out there, to me it boils down to one extremely simple principle:

- I want to tell the computer what to do, I don't want the computer to tell me what to do.

Apple/iPhone/Mac tells you what to do and there is usually only one way, too.
Windows/Android - you're in charge, you tell the machine what to do, and you learn how and stumble around a bit perhaps but you're still in charge. I prefer that.
 

Users who are viewing this thread

Back
Top Bottom