A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX control

[pdanes]

Update - the user bought Office 365 and tried installing it - same error. Now I'm completely confused.

It appears that something is well and truly effed in the machine as a whole, since three different version of Access throw the same error, in an app that works perfectly everywhere else. But I can't even begin to guess what that might be.

I can connect to the machine again and try building a small app, and see if I can make a it start misbehaving at some point, like when I put event code onto some controls. But even if I do that and pinpoint exactly where the mess starts misbehaving (adding an event call), what will that tell me, and what do I do about it? This is as confusing a situation as I have ever encountered in all my years of working with Access.

 

[arnelgp]

check all your forms/reports Controls (labels, textbox, etc).
if there are that have non-english name, change them.

 

[tvanstiphout]

Humor me, and as a test take the Ribbon and its table out of the equation.

 

[pdanes]

check all your forms/reports Controls (labels, textbox, etc).
if there are that have non-english name, change them.

They do not. I am very careful to avoid ALL such names, everywhere. Strictly US A-Za-z, numbers and underscores. No spaces, no special characters, no foreign characters. The only place I use non-English characters is comments, and label or field captions on forms and reports. And of course, I must allow them in the data.

 

[pdanes]

Humor me, and as a test take the Ribbon and its table out of the equation.

Okay. At this point, I'm willing to try anything. I'll post back what happens.

 

[pdanes]

Humor me, and as a test take the Ribbon and its table out of the equation.

Ribbon table completely removed. No change. But in the process, I discovered something else odd - starting the app with Shift does NOT start it the way I would expect - side panel visible and start code not executed. It still insists on trying to start the start-up form. And of course, still fails with that same error message.

 

[pdanes]

Humor me, and as a test take the Ribbon and its table out of the equation.

I also just now removed the table that has some images for the ribbon, and the only table in the entire DB that has OLE fields. C & R after removal. No change.

 

[pdanes]

I just tried making a copy of one of the datasheet subforms, and starting it alone. If I clear out ALL the event calls, it opens normally, in all three modes: datasheet view, single-record view and continuous view. If I have ANY event code links, it throws the error, and after I click away the error, it opens, but never actually calls any of the event code. When I have event code tied to some of the fields, clicking on such a field throws the error, but never fires the code (breakpoint right on the entry point of the code).

 

[MsAccessNL]

I didn’t read your whole post. I had an error once, which I couldn’t solve. I found a way to trap the error.

Private Sub Form_Error(DataErr As Integer, Response As Integer) If DataErr = 2684 Then Response = acDataErrContinue
End Sub

 

[MsAccessNL]

I didn’t read your whole post. I had an error once, which I couldn’t solve. I found a way to trap the error. It had to do with an empty ole object.

Private Sub Form_Error(DataErr As Integer, Response As Integer) If DataErr = 2684 Then Response = acDataErrContinue
End Sub

 

[pdanes]

I didn’t read your whole post. I had an error once, which I couldn’t solve. I found a way to trap the error. It had to do with an empty ole object.

Thank you, I tried that. Same thing - it throws the error and never executes the code.

 

[arnelgp]

maybe upload your db?

 

[pdanes]

maybe upload your db?

Even almost emptied and zipped, it's almost 20 MB. Don't know what the limit is in this forum, but that exceeds it. It is available to download on a large file transfer site: https://www.uschovna.cz/zasilka/OXW8ZK4BDKLW429B-JXX

 

[arnelgp]

what is the original extension? i replaced it with .accdb and .mdb and both did not open in Access?

 

[arnelgp]

there is error opening query ZaznamyProDS (the recordsource of your subform), try fixing it.

 

[pdanes]

what is the original extension? i replaced it with .accdb and .mdb and both did not open in Access?

.ZIP

 

[pdanes]

there is error opening query ZaznamyProDS (the recordsource of your subform), try fixing it.

The error is when I open that subform, or any one of several similar forms. The query itself works fine, as do all the queries for all such forms.

 

[zGuanchen]

Not sure if you've manage the problem. But I'm also posting here that may help others. I'm also seeing the error like:

The expression After Insert you entered as the event property setting produced the following error: A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control.
* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
* There may have been an error evaluating the function, event, or macro.

The problem comes from one of the column titles. The original column title comes from a non-English OS. I solved it by renaming the column title.

The language, locale, encoding, whatever it's called in the programming world is very confusing to me, till today.

I'm not sure if the non-English word in the data also causes the error.
I'm also not sure when I define the column in English OS, will it cause error when my colleague using the application in German OS. Let's see...

 

[pdanes]

Not sure if you've manage the problem. But I'm also posting here that may help others. I'm also seeing the error like:

The problem comes from one of the column titles. The original column title comes from a non-English OS. I solved it by renaming the column title.

The language, locale, encoding, whatever it's called in the programming world is very confusing to me, till today.

I'm not sure if the non-English word in the data also causes the error.
I'm also not sure when I define the column in English OS, will it cause error when my colleague using the application in German OS. Let's see...

Thank you, I did finally get that working. Never did solve the actual problem here, but a bit further down the road, I encountered another similar issue with this DB, and finally tracked it down to a 32-bit version of Stephen Lebans' PictureBox class. Lebans has quit Access, but some genius on this forum supplied me with a version of the class ported to 64 bits, fixing the problem completely and earning my eternal gratitude.

 

[The_Doc_Man]

Thank you for posting the solution. Linking it back to a bitness conflict will help future browsers looking for similar problems to yours!