Access Error Message

First thing to check is References...

http://www.access-diva.com/d5.html

Second thing to check is Trusted Locations...

http://www.access-diva.com/d4.html

I agree with Gina in principle, but I am struck with this part of the error message: "Microsoft Access was communicating with the OLE server or ActiveX control". Do you have any (perhaps accidental) ActiveX controls on the form? Are you using OLE Automation in the code-behind?

Ben=RazillHamid,

While that fix may have worked for you that would not be the recommended fix for this particular issue.  Two of those files will cause your Access file issues and/or crash once upgraded...

Srchui.dll

OWC11.dll

Depending on your version of Access, you may actually be able to remove those References.  See...

Repair (or Remove) Missing or Broken References

This will probably fix it, i had same problem, the form or report needs parameters before it open, especially if it is trying to run a query which relies on them aswell, in your form or report Open function in VB put something like the following

Dim rst As DAO.Recordset

Dim db As DAO.Database

Dim qdf As QueryDef

Dim frm As Form

Set db = CurrentDb

Set frm = Forms!reporting

Set qdf = db.QueryDefs("DataCrosstab1")

qdf.Parameters("[Forms]![Reporting]![System]") = frm.System

qdf.Parameters("[Forms]![Reporting]![start]") = frm.start

qdf.Parameters("[Forms]![Reporting]![end]") = frm.end

qdf.Parameters("[Forms]![Reporting]![area]") = frm.Area

qdf.Parameters("[Forms]![Reporting]![phase]") = frm.Phase

Obviously just change your paramters to the ones it is looking for, in the example above i am trying to open forms.reporting and the error occurs, this fixes mine

I solved this for one user in Access by changing the setting 'compile on demand' from the options/general tab in the vba editor.

How does one put VBA in the event property instead of the event itself?  How do these things differ? What does this mean precisely? How can it come about? How could I find instances of this in my code? Usually, I just click on the appropriate property and it takes me to the VBA for the event handler.

create function (not a sub), then put it into the event property:

not much difference really.

the only benefit I can think about, is that if you copy/paste such control, then the property comes with the control, and you do not need to copy event handler after that.

to find instances of such properties, I suggest using Find & Replace utility (http://www.rickworld.com/products.html), which can search properties across the database.