OLE or Active X Control Error

[WCStarks]

A simple On Current Event code that used to work just fine, started producing an error yesterday, that I do not know how to resolve.

Private Sub Form_Current()
[Mem_Name] = [Surname] & ", " & [Given Name]
End Sub

While making sure the "Use Wizard Controls" was active, the only thing I can think of that I did earlier yesterday, that may be related at all, was under the "Design > Controls > Active X Controls", which I clicked on to see what it was about. But, not knowing how to do anything with the resulting list, I simply canceled it. That may not have anything to do with the error. I don't know.



When I remove the On Current code, the error goes away. When I put it back in, the error returns. I have no idea how to find or fix the underlying problem, so the code will work again.

Apparently this problem is even broader than I originally thought. I now get the following error on the same form when I attempt to go to a record:
A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control.


Close the OLE server and restart it outside of Microsoft Access. Then try the original operation again in Microsoft Access.

[June7]

Have you run Compact & Repair?

If that doesn't fix, might have to rebuild the form.

[WCStarks]

I did. More than once. I also turned my computer off and rebooted it. From reading about this issue online, it sounds like the problem may be outside of Access. I just tried it on a different computer and it does not have the problem. So, the problem is apparently with my computer/OLE/Active X software. I just ran a virus check of my computer, but none found.

[June7]

Ugh! Uninstall/reinstall Access?

Is bizarre. I have looked at the ActiveX controls list a number of times and never caused issue with code.

[WCStarks]

I am not saying that just looking at the Active X Controls actually caused it. It suppose it did not. I just mentioned it, as it was the closest thing, I could think of, that might have been related.

Now, I cannot use Access' Find record function either, or I get the second message is posted. I can still browse from record to record in the form, but I cannot use those functions.

[Missinglinq]

This type of error usually, but not always, associated with opening a Form, is apparently caused by all kinds of things, and, to the best of my knowledge, it is very seldom, if ever, actually connected with communicating with a OLE server or ActiveX Control!

The most common cause, going by what I've seen online for the past ten years, has to do with using a non-English language with Access, and the need to set the language for non-unicode programs to that foreign language. Here's a link explaining this:

You receive an error message when you start Visual Basic for Applications code in an Access database

And since the OnCurrent event fires, immediately a Bound Form loads, it kind of makes sense that Access would associate the error with that event.

Linq ;0)>

[WCStarks]

Well, I don't think it would be related to language. However, I did change how the dates formatted in access. This same db would run without a problem on another computer on my same Office 365 account, and on my Son-In-Law's computer on a different 365 account, without any problem. But on my main computer, as long as that On Current code is there, the error occurs. I finally tried a backup copy of the db from that morning, and the error went away. Very strange.