[AccessD] Access error - A problem occurred while Microsoft Access was communicating with the OLE server or Active X Control.

Charlotte Foust charlotte.foust at gmail.com
Fri Sep 20 14:28:36 CDT 2013


Try using a query instead of the table as the datasource.  Then you can
open the query directly to see whether it runs independent of the form.

Charlotte


On Fri, Sep 20, 2013 at 11:38 AM, Doug Murphy <dw-murphy at cox.net> wrote:

> Folks,
>
> This is driving me nuts. I created a new Access 2010, accdb database.
> Created some tables. Created one form with one table as the recordsource.
> The form has a total of 269 controls on it, labels, text boxes, etc. There
> is no code on the form aside from a close button that runs 'Docmd.close'.
> When I attempt to close the form using the button I get an Access error " A
> problem occurred while Microsoft Access was communicating with the OLE
> server or Active X Control.". The error is thrown before the code runs.
> Can't catch it with a break point. If I substitute a macro it closes fine.
> What can be causing this? I have compacted, decompiled/compiled/compacted,
> imported into a new database container, exported form to text and
> re-imported and still get the error. Tried putting the file on another
> computer to see if my version of Access corrupted somehow. Get the same
> error there.
>
> Looked in this form and general Google search and cannot find a cause. Any
> good ideas. I need to be able to put some VBA behind this form.
>
> Thanks in advance.
>
> Doug
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list