Doug Murphy
dw-murphy at cox.net
Fri Sep 20 14:08:38 CDT 2013
That is what I use, I just shorted the explanation. This is the first time I have seen this. The only thing I can think of is that it is the number of controls on the form, but the limit is supposed to be 754. I have not exceeded that even with edits, deletes, etc. Very frustrating. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Friday, September 20, 2013 11:53 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access error - A problem occurred while Microsoft Access was communicating with the OLE server or Active X Control. Hi Doug, Try being specific with what you're closing: DoCmd.Close acform, Me.Name, acSaveNo Just a guess ... Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Friday, September 20, 2013 1:39 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Access error - A problem occurred while Microsoft Access was communicating with the OLE server or Active X Control. 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 -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com