Active x Control when no access controls

[gem1204]

I received this error before


"a problem occurred while microsoft access was communicating with the ole server or ActiveX control

I received this error again on a database I had just created. I had created several buttons along with some code, then all of a sudden I got the active X control error every time I clicked on one of the buttons. I deleted all of the code and created a simple Msgbox("Click") and even that didn't work. I couldn't even create code behind another new button. This was a simple database I had just started on and there were only 4 tables and a couple of forms. I'm not using any ActiveX controls or anything other than just the standard controls. Compacting and repairing the database, compiling, opening and closing Access, restarting the computer.... none of those worked. I have one other form with some code in this database and that works just fine.

In the past I've had to just re-create the form and basically start over.

Has anyone else had this problem or does anyone know how to fix it or prevent it?

I'm using ms access 2016

[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 always a possible solution, when things suddenly go phooey, for no apparent reason, is to create a new, blank Access file and Import everything into it.

Linq ;0)>

[June7]

Sometimes weirdness just has to be attributed to corruption that cannot be explained and the only fix is to rebuild.

[gem1204]

Thanks for the responses. After starting my most I ran across possible cause. I'm using dual monitors and opening the code view while the form is running can sometimes cause this error. I know that I sometimes do this even though its a bad practice. I have to admit that I do that often

[June7]

Why would having VBA editor open cause an issue? Never experienced this with dual monitors.

[davegri]

Try importing your existing db into a new empty db.